04-23-2024, 10:37 AM
Like many of you, I came across the work that @Fishwaldo did to get Linux working on the Star64.
I'm new to Yocto and the lower level of building Linux for embedded systems. I would love it if someone/Fishwaldo could do an ELI5 on what he did for the `meta-pine64` layer (btw, there seems to be a different `meta-pine64` layer mentioned on the openembedded page but that's specifically for ARM chips).
From what I understand:
1. He forked/branched off the Linux kernel.
2. Applied OEM drivers as patches from StarFive.
3. Used that in the new Yocto layer he built.
My questions (for now) are:
1. How did he/you guys find the U-boot partition map? I have seen the JH7110 Boot User Guide, but I haven't been able to figure out how U-boot mentions the partition sizes in their documentation.
2. I couldn't quite find where StarFive mentions that their drivers are not compatible with the newer 6.1xx Linux kernel, forcing @Fishwaldo to use the 5.1xx kernel. Ideally, one would be able to download the source tree and place the patches in the tree to compile it with bitbake in Yocto, yes?
Would greatly appreciate any replies to this thread! I'm very new to this, and I would like to be a part of the effort to take RISC-V forward, even if I'm only doing it for myself. I'm looking at the Star64 alongside the OSEdge as an alternative to Coral.ai's TPUs and would like to learn to build my images for both of them.
Thanks!
I'm new to Yocto and the lower level of building Linux for embedded systems. I would love it if someone/Fishwaldo could do an ELI5 on what he did for the `meta-pine64` layer (btw, there seems to be a different `meta-pine64` layer mentioned on the openembedded page but that's specifically for ARM chips).
From what I understand:
1. He forked/branched off the Linux kernel.
2. Applied OEM drivers as patches from StarFive.
3. Used that in the new Yocto layer he built.
My questions (for now) are:
1. How did he/you guys find the U-boot partition map? I have seen the JH7110 Boot User Guide, but I haven't been able to figure out how U-boot mentions the partition sizes in their documentation.
2. I couldn't quite find where StarFive mentions that their drivers are not compatible with the newer 6.1xx Linux kernel, forcing @Fishwaldo to use the 5.1xx kernel. Ideally, one would be able to download the source tree and place the patches in the tree to compile it with bitbake in Yocto, yes?
Would greatly appreciate any replies to this thread! I'm very new to this, and I would like to be a part of the effort to take RISC-V forward, even if I'm only doing it for myself. I'm looking at the Star64 alongside the OSEdge as an alternative to Coral.ai's TPUs and would like to learn to build my images for both of them.
Thanks!