I was able to boot my Raspberry Pi using the Pi Imager and the Fedora AARCH64 Raw Image. While this makes me happy, I don’t really understand what these pieces are. So, I want to take a little more look at them.Continue reading
We are trying to enable the graphics hardware subsystem on the Raspberry Pi 4. This driver lives in mesa. The current Centos mesa.spec file does not enable the V3D Driver we need. Here are the steps I am going through to build the driver and integrate it into the meta-rpm build.Continue reading
I wanted to see how my work had diverged from the standard Raspberry Pi build. Specifically, the image creation stage is failing in my work. I can run the script in the original (upstream) version by doing thing following.Continue reading
config.sub is used to determine, among other things, the architecture of the machine. This is used in the configure script for an autotools based make file.
Older config.sub files don’t know how to handle aarch64, the generic name used for ARM64 servers in the build process. We have a recipe that pulls in code using an older config.sub file and I need to update.
My first approach was to build a patch. This works fine, and it was my fallback, but it is tedious to do for every recipe that needs this update, every time it needs it. It turns out we have a better approach that follows the guide of “don’t repeat yourself.”Continue reading
Many hardware vendors use Yocto as a way to provide a version of the Linux Kernel and board bring up package. This is a very Linux-from-scratch type approach that grew out of GenToo. My current work is on closing the gap between these vendors and the RPM based code management approach in Fedora etc.
This is a lot of fun.
Our code repository is on gitlab.
I’ll be posting some of the more interesting things that I learn while working on this.