buildroot VS linux-xlnx

I did it few times. It's so much easier nowadays with https://buildroot.org/

If you dig through the rootfs of the K1 it becomes clear that Creality is using buildroot so we should be able to do that ourselves - at least some of us.

An embedded system like Roku doesn't need to "run everything", it just needs to run their "platform", which is probably quite small. It's pretty trivial to assemble your own OS from "off-the-shelf" components. You can use something like buildroot to spin up a new OS in half a day, using only the components you want. You can also use "smaller" components that have far fewer features, meaning less bugs and less updates.

https://github.com/buildroot/buildroot

> I do this for every Windows installation that is used for similar purposes, like embedded machines that has to run a single application, virtual machines, etc.

Have you tried running Linux for these use cases? This sort of thing is an area Linux excels, in my experience.

When you run Windows, you're in for the whole kit and caboodle. Most of the components are proprietary, closed-source black boxes. You can only poke and prod and test and hope things don't break in unexpected ways.

Conversely, Linux can be easy stripped down to a bare bones kernel and a single statically-linked binary. I can run a useful application on top of Linux with the whole system weighing in smaller than bootmgfw.efi.

Something more complex, but still custom, is easily crafted with Buildroot.

https://buildroot.org/

Have a look at the commit history of Linux or buildroot for nice readable commit histories.

Gentoo could teach you more about what is involved in dependency handling and actual ‘construction’ of a Linux system. But Linux From Scratch is a much better teaching tool for learning this, and even things like Buildroot are arguably better than Gentoo for this because they generally force you to care about a lot of the stuff that Gentoo hides away to make the system nicer to use.

For the DMA I found several examples by xilinx and independent folks demonstrating several way in which it can be done in linux. I started with the xilinx_dma.c driver that is provided by xilinx along with a test driver that is found here. Long story short, it didn't work. The test failed and nothing came of it.

The Framebuffer Read IP has kernel driver and you can find the device tree bindings for it here.

Has anyone used custom configurations on the Xilinx KV260 AP1302 Image co-processor? I plan to look at the different camera options for Kria KV260. The documentation is not publicly available. This was the only code I could find: https://github.com/Xilinx/linux-xlnx/blob/master/drivers/media/i2c/ap1302.c

Thank you for your response. The remote repo I was pointing to was Xilinx/linux-xlnx, but I was pointing to a branch with an older commit, which was the default version for PetaLinux 2018.3: Xilinx/linux-xlnx/tree/xlnx_rebase_v4.14

https://github.com/Xilinx/linux-xlnx the petalinux repo has some history, I don't know how long it goes back though (I am with the phone)

Linux-Xlnx – The official Linux kernel from Xilinx\ (3 comments)