Would it be possible to get a newer raspberrypi-firmware-1 rollup, apparently "recent" firmware updates fix this bug https://github.com/raspberrypi/linux/issues/624 I guess git hash 1bb122bcd82bcd308ffbf3a86084ae02841ac73b includes the fix and is as good as any? Reproducible: Always
I'm currently testing it in my overlay (layman -s xmw).
I was very confused by their firmware versioning. The version in comment #1 works for me. But a month or so ago when I decided to update to the 3.18 rpi git tree, I figured I'd update the firmware as well. I could _not_ get recent firmwares to boot. Neither with my spit-rolled kernels, nor with their prebuilt ones. I have a RPi ver B, with 512MB ram (not a B+, or a ver2). Do you have any light to shed? It wouldn't even boot with the coloured test-pattern, nothing came out of the serial debug port, just a dead board until I back-tracked. I haven't found time yet to bisect the firmware tree and figure it out deeper.
Created attachment 403870 [details] firmware-9999 to match -sources-9999 and userland-9999 I do not create the config.txt and cmdline.txt files, but I might add an einfo at the end. I also plan to add use flags kernel-only, opt-only and firmware-only That way we don't overwrite the work we are dealing with while keeping in sync and abled to be supported in the raspberrypi forums. ( a bit better) Probably should have -* in KEYWORDS too...
Created attachment 403882 [details] Newer better version Useflag for installing the kernel and userland separately. Nerdboy would like to add a opengl flag to install the libs under /usr/lib/opengl/profiles. This has been tested on Armv6j and Armv7a the Rpi B+ and Rpi 2
should we merge the packages into rasperrypi-firmware[kernel,loader,userland] or stick to rasperrypi-firmware (fka -loader), rasperrypi-kernel, and rasperrypi-userland-bin? I'm undecided. All these origin from the same -- now released -- 100M tarball and multiple verifications during three merges are redundant, you most likely want all from the same version. General package guideline would recommend three packages for modulare management instead of rebuild due useflag changes.
I do use all the packages separately in order to test different things. I do think the use flag depends might be a bit tricky when the functionality overlaps. But then, one of them installs the userland in ${ROOT} while the other installs in /opt firmware is the easy not fuss install for 90% of the people and it follows the Rpi kernel. I simply copy the .config in /usr/src/linux and the emerge who need to check for features are usually happy. No real need to download the whole source.
commit bb14be4e393875fb1cf094c6f70c2af042c388e9 Author: Michael Weber <xmw@gentoo.org> Date: Fri Feb 19 22:45:29 2016 +0100 sys-boot/raspberrypi-firmware: Version bump (bug 521920). commit 2d8004aedbcaf2b78c7c03744e8c766e65c029e4 Author: Michael Weber <xmw@gentoo.org> Date: Fri Feb 19 22:42:37 2016 +0100 sys-boot/raspberrypi-firmware: drop old versions.
commit db6e7b65fb0df095794247c36fc1bb3e78791738 Author: Michael Weber <xmw@gentoo.org> Date: Fri Feb 19 23:46:55 2016 +0100 sys-kernel/raspberrypi-image: Version bump (bug 521920). Package-Manager: portage-2.2.27 sys-kernel/raspberrypi-image/Manifest sys-kernel/raspberrypi-image/raspberrypi-image-4.1.17_p20160209.ebuild commit 3c20fbf00809ed5c4988f91a504c8a2f3bebf5c3 Author: Michael Weber <xmw@gentoo.org> Date: Fri Feb 19 23:09:29 2016 +0100 media-libs/raspberrypi-userland-bin: Initial import for bug 521920. Package-Manager: portage-2.2.27 media-libs/raspberrypi-userland-bin/Manifest media-libs/raspberrypi-userland-bin/files/04raspberrypi-userland-bin media-libs/raspberrypi-userland-bin/metadata.xml media-libs/raspberrypi-userland-bin/raspberrypi-userland-bin-1.20160209.ebuild
Please use these three packages for the full firmware release bundle: =media-libs/raspberrypi-userland-bin-1.20160209::gentoo[hardfp?] =sys-boot/raspberrypi-firmware-1.20160209::gentoo =sys-kernel/raspberrypi-image-4.1.17_p20160209::gentoo
