| Message ID | 1488729976-7116-5-git-send-email-martin@barkynet.com |
|---|---|
| State | Accepted |
| Headers | show |
Hi, On 03/05/2017 05:06 PM, Martin Bark wrote: > -RPI_FIRMWARE_VERSION = 7f8ac8dac0b80291cbf5e56580139034a0a42070 > +RPI_FIRMWARE_VERSION = 78c4983379de0537f49a97fb37ceaaf42632b28c New firmware version does not get along with projects that still use 4.4.x kernel. It seems that projects that still use 4.4.x are now supposed to use the firmware branch called "stable" Perhaps we should introduce a config option for firmware version, like we have for kernel version? Yours sincerely, Floris Bos
>>>>> "Floris" == Floris Bos <bos@je-eigen-domein.nl> writes: > Hi, > On 03/05/2017 05:06 PM, Martin Bark wrote: >> -RPI_FIRMWARE_VERSION = 7f8ac8dac0b80291cbf5e56580139034a0a42070 >> +RPI_FIRMWARE_VERSION = 78c4983379de0537f49a97fb37ceaaf42632b28c > New firmware version does not get along with projects that still use > 4.4.x kernel. > It seems that projects that still use 4.4.x are now supposed to use > the firmware branch called "stable" > Perhaps we should introduce a config option for firmware version, like > we have for kernel version? Gaah :/ Have you brought this up with rpi upstream? What is their feedback?
On 03/10/2017 02:20 PM, Peter Korsgaard wrote: > > On 03/05/2017 05:06 PM, Martin Bark wrote: > >> -RPI_FIRMWARE_VERSION = 7f8ac8dac0b80291cbf5e56580139034a0a42070 > >> +RPI_FIRMWARE_VERSION = 78c4983379de0537f49a97fb37ceaaf42632b28c > > > New firmware version does not get along with projects that still use > > 4.4.x kernel. > > It seems that projects that still use 4.4.x are now supposed to use > > the firmware branch called "stable" > > > Perhaps we should introduce a config option for firmware version, like > > we have for kernel version? > > Gaah :/ Have you brought this up with rpi upstream? What is their > feedback? Ok, turns out the new firmware can still boot 4.4.x, as long as you compile the device tree files from kernel source. The bundled binary ones only work for 4.9. Should have known that, as I had already been burned by that before... BTW is it possible to let buildroot compile dt overlays nowadays? As the overlays are now also starting to show changes between versions. E.g.: https://github.com/raspberrypi/linux/blob/rpi-4.4.y/arch/arm/boot/dts/overlays/vc4-kms-v3d-overlay.dts versus https://github.com/raspberrypi/linux/blob/rpi-4.9.y/arch/arm/boot/dts/overlays/vc4-kms-v3d-overlay.dts Yours sincerely, Floris Bos
Floris Bos, On 10 March 2017 at 20:05, Floris Bos <bos@je-eigen-domein.nl> wrote: > On 03/10/2017 02:20 PM, Peter Korsgaard wrote: > >> > On 03/05/2017 05:06 PM, Martin Bark wrote: >> >> -RPI_FIRMWARE_VERSION = 7f8ac8dac0b80291cbf5e56580139034a0a42070 >> >> +RPI_FIRMWARE_VERSION = 78c4983379de0537f49a97fb37ceaaf42632b28c >> >> > New firmware version does not get along with projects that still use >> > 4.4.x kernel. >> > It seems that projects that still use 4.4.x are now supposed to use >> > the firmware branch called "stable" >> >> > Perhaps we should introduce a config option for firmware version, like >> > we have for kernel version? >> >> Gaah :/ Have you brought this up with rpi upstream? What is their >> feedback? >> > > Ok, turns out the new firmware can still boot 4.4.x, as long as you > compile the device tree files from kernel source. > The bundled binary ones only work for 4.9. > > > Should have known that, as I had already been burned by that before... > > BTW is it possible to let buildroot compile dt overlays nowadays? > As the overlays are now also starting to show changes between versions. > You can build individual overlays by adding them to BR2_LINUX_KERNEL_INTREE_DTS_NAME. For example adding overlays/gpio-poweroff-overlay to BR2_LINUX_KERNEL_INTREE_DTS_NAME will build gpio-poweroff-overlay.dtb into the output/images directory. Thanks Martin > > E.g.: > > https://github.com/raspberrypi/linux/blob/rpi-4.4.y/arch/ > arm/boot/dts/overlays/vc4-kms-v3d-overlay.dts > versus > https://github.com/raspberrypi/linux/blob/rpi-4.9.y/arch/ > arm/boot/dts/overlays/vc4-kms-v3d-overlay.dts > > > > Yours sincerely, > > Floris Bos > > > _______________________________________________ > buildroot mailing list > buildroot@busybox.net > http://lists.busybox.net/mailman/listinfo/buildroot >
On 03/12/2017 06:26 PM, Martin Bark wrote: > Floris Bos, > > On 10 March 2017 at 20:05, Floris Bos <bos@je-eigen-domein.nl > <mailto:bos@je-eigen-domein.nl>> wrote: > > On 03/10/2017 02:20 PM, Peter Korsgaard wrote: > > > On 03/05/2017 05:06 PM, Martin Bark wrote: > >> -RPI_FIRMWARE_VERSION = > 7f8ac8dac0b80291cbf5e56580139034a0a42070 > >> +RPI_FIRMWARE_VERSION = > 78c4983379de0537f49a97fb37ceaaf42632b28c > > > New firmware version does not get along with projects that > still use > > 4.4.x kernel. > > It seems that projects that still use 4.4.x are now > supposed to use > > the firmware branch called "stable" > > > Perhaps we should introduce a config option for firmware > version, like > > we have for kernel version? > > Gaah :/ Have you brought this up with rpi upstream? What is their > feedback? > > > Ok, turns out the new firmware can still boot 4.4.x, as long as > you compile the device tree files from kernel source. > The bundled binary ones only work for 4.9. > > > Should have known that, as I had already been burned by that before... > > BTW is it possible to let buildroot compile dt overlays nowadays? > As the overlays are now also starting to show changes between > versions. > > > You can build individual overlays by adding them > to BR2_LINUX_KERNEL_INTREE_DTS_NAME. For example adding > overlays/gpio-poweroff-overlay to BR2_LINUX_KERNEL_INTREE_DTS_NAME > will build gpio-poweroff-overlay.dtb into the output/images directory. The firmware would expect that file to be called "overlays/gpio-poweroff.dtbo" though. So would require a post-installation script to fix up the file names. Not the most ideal solution. Yours sincerely, Floris Bos
diff --git a/package/rpi-firmware/rpi-firmware.hash b/package/rpi-firmware/rpi-firmware.hash index 8161d7a..f6dd03a 100644 --- a/package/rpi-firmware/rpi-firmware.hash +++ b/package/rpi-firmware/rpi-firmware.hash @@ -1,2 +1,2 @@ # Locally computed -sha256 144de63ee1999155fc1ff597630f1a13f798e597e7c4d144b8b625fa774c1f9b rpi-firmware-7f8ac8dac0b80291cbf5e56580139034a0a42070.tar.gz +sha256 0797a034b33a0218fd6fb3c5bb1473959e209a8fe676f3c215f954806601aa78 rpi-firmware-78c4983379de0537f49a97fb37ceaaf42632b28c.tar.gz diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk index d2cd481..b73ef53 100644 --- a/package/rpi-firmware/rpi-firmware.mk +++ b/package/rpi-firmware/rpi-firmware.mk @@ -4,7 +4,7 @@ # ################################################################################ -RPI_FIRMWARE_VERSION = 7f8ac8dac0b80291cbf5e56580139034a0a42070 +RPI_FIRMWARE_VERSION = 78c4983379de0537f49a97fb37ceaaf42632b28c RPI_FIRMWARE_SITE = $(call github,raspberrypi,firmware,$(RPI_FIRMWARE_VERSION)) RPI_FIRMWARE_LICENSE = BSD-3c RPI_FIRMWARE_LICENSE_FILES = boot/LICENCE.broadcom
Signed-off-by: Martin Bark <martin@barkynet.com> --- package/rpi-firmware/rpi-firmware.hash | 2 +- package/rpi-firmware/rpi-firmware.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)