hexelpdkk wrote:Hi Vaughan,
I see you have an F23 minimal now, good work!
Yes I uploaded it a few days ago but didn't say anything as its all a bit bleeding edge. I wanted to use it for a week or so and see how it was behaving. It uses a kernel based on the newer rpi-4.2.y branch and I not exactly sure how stable that is (seems pretty good so far).
What is the process to create the rpms in the first place? For something like the firmware, I guess you just copy/clone rpi/firmware objects and rpmbuild.
Yes, I just clone the appropriate rpi git repo and simply package it up.
How do you produce the kernel rpm? Is the kernel source linux + fedora patches + rpi patches, or rpi source + fedora patches?
For the kernel, I diff the appropriate mainline and rpi git repos and then apply the generated patch to official kernel.org sources at build time. I do it this way as all changes to kernel.org sources are then clearer and more obvious. Everyone can see exactly what has changed as compared to mainline kernel sources, just by looking at the patch. The alternative of packaging up a rpi git repo snapshot and building a kernel from it essentially obfuscates changes, as compared to the mainline kernel. If done this way, you better be able to trust the packager, as changes are not obvious, harder to find and therefore its easier for nefarious people to hide stuff.
I don't need / use any Fedora specific patches at present (except one which I keep forgetting to flick) as the majority of patches are simply not applicable to our bcm2709/bcm2836 boards. They are for different archs, other arm devices/quirks which are not applicable, or various other bits and pieces that are not essential. If needed (or asked) I can pull in patches when required but for the moment the resulting kernel source is essentially the rpi git branch source.