configs/raspberrypi*: bump kernel version to 877656cd14
PATCH 1/2 configs/raspberrypi*: bump kernel version to 877656cd14
Now based on 4.14.98 (from 4.14.95)
--- configs/raspberrypi0_defconfig | 2 +- configs/raspberrypi0w_defconfig | 2 +- configs/raspberrypi2_defconfig | 2 +- configs/raspberrypi3_64_defconfig | 2 +- configs/raspberrypi3_defconfig | 2 +- configs/raspberrypi3_qt5we_defconfig | 2 +- configs/raspberrypi_defconfig | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-)
configs/raspberrypi0_defconfig +1 -1
@@ -9,7 +9,7 @@ BR2_TOOLCHAIN_BUILDROOT_CXX=y BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_CUSTOM_TARBALL=y -BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,83b36f98e1a48d143f0b466fcf9f8c4e382c9a1c)/linux-83b36f98e1a48d143f0b466fcf9f8c4e382c9a1c.tar.gz" +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,877656cd145497db7c09a7de06ea85db98bd72a3)/linux-877656cd145497db7c09a7de06ea85db98bd72a3.tar.gz" BR2_LINUX_KERNEL_DEFCONFIG="bcmrpi" # Build the DTBs for A/B from the kernel sources: the zero is the same
configs/raspberrypi0w_defconfig +1 -1
@@ -9,7 +9,7 @@ BR2_TOOLCHAIN_BUILDROOT_CXX=y BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_CUSTOM_TARBALL=y -BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,83b36f98e1a48d143f0b466fcf9f8c4e382c9a1c)/linux-83b36f98e1a48d143f0b466fcf9f8c4e382c9a1c.tar.gz" +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,877656cd145497db7c09a7de06ea85db98bd72a3)/linux-877656cd145497db7c09a7de06ea85db98bd72a3.tar.gz" BR2_LINUX_KERNEL_DEFCONFIG="bcmrpi" BR2_LINUX_KERNEL_DTS_SUPPORT=y BR2_LINUX_KERNEL_INTREE_DTS_NAME="bcm2708-rpi-0-w"
configs/raspberrypi2_defconfig +1 -1
@@ -12,7 +12,7 @@ BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_14=y BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_CUSTOM_TARBALL=y -BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,83b36f98e1a48d143f0b466fcf9f8c4e382c9a1c)/linux-83b36f98e1a48d143f0b466fcf9f8c4e382c9a1c.tar.gz" +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,877656cd145497db7c09a7de06ea85db98bd72a3)/linux-877656cd145497db7c09a7de06ea85db98bd72a3.tar.gz" BR2_LINUX_KERNEL_DEFCONFIG="bcm2709" # Build the DTB from the kernel sources
configs/raspberrypi3_64_defconfig +1 -1
@@ -11,7 +11,7 @@ BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_14=y BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_CUSTOM_TARBALL=y -BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,83b36f98e1a48d143f0b466fcf9f8c4e382c9a1c)/linux-83b36f98e1a48d143f0b466fcf9f8c4e382c9a1c.tar.gz" +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,877656cd145497db7c09a7de06ea85db98bd72a3)/linux-877656cd145497db7c09a7de06ea85db98bd72a3.tar.gz" BR2_LINUX_KERNEL_DEFCONFIG="bcmrpi3" # Build the DTB from the kernel sources
configs/raspberrypi3_defconfig +1 -1
@@ -11,7 +11,7 @@ BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_14=y BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_CUSTOM_TARBALL=y -BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,83b36f98e1a48d143f0b466fcf9f8c4e382c9a1c)/linux-83b36f98e1a48d143f0b466fcf9f8c4e382c9a1c.tar.gz" +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,877656cd145497db7c09a7de06ea85db98bd72a3)/linux-877656cd145497db7c09a7de06ea85db98bd72a3.tar.gz" BR2_LINUX_KERNEL_DEFCONFIG="bcm2709" # Build the DTB from the kernel sources
configs/raspberrypi3_qt5we_defconfig +1 -1
@@ -12,7 +12,7 @@ BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_14=y BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_CUSTOM_TARBALL=y -BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,83b36f98e1a48d143f0b466fcf9f8c4e382c9a1c)/linux-83b36f98e1a48d143f0b466fcf9f8c4e382c9a1c.tar.gz" +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,877656cd145497db7c09a7de06ea85db98bd72a3)/linux-877656cd145497db7c09a7de06ea85db98bd72a3.tar.gz" BR2_LINUX_KERNEL_DEFCONFIG="bcm2709" # Build the DTB from the kernel sources
configs/raspberrypi_defconfig +1 -1
@@ -11,7 +11,7 @@ BR2_TOOLCHAIN_BUILDROOT_CXX=y BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_CUSTOM_TARBALL=y -BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,83b36f98e1a48d143f0b466fcf9f8c4e382c9a1c)/linux-83b36f98e1a48d143f0b466fcf9f8c4e382c9a1c.tar.gz" +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,877656cd145497db7c09a7de06ea85db98bd72a3)/linux-877656cd145497db7c09a7de06ea85db98bd72a3.tar.gz" BR2_LINUX_KERNEL_DEFCONFIG="bcmrpi" # Build the DTBs for A/B, A+/B+ and compute module from the kernel sources
Signature · 1 line
2.20.1
PATCH 2/2 package/rpi-firmware: bump version to 83977fe3b6
--- package/rpi-firmware/rpi-firmware.hash | 2 +- package/rpi-firmware/rpi-firmware.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
package/rpi-firmware/rpi-firmware.hash +1 -1
@@ -1,2 +1,2 @@ # Locally computed -sha256 f1d631920ed4ae15f368ba7b8b3caa4ed604f5223372cc6debbd39a101eb8d74 rpi-firmware-81cca1a9380c828299e884dba5efd0d4acb39e8d.tar.gz +sha256 9a34ccc4a51695a33206cc6c8534f615ba5a30fcbce5fa3add400ecc6b80ad8a rpi-firmware-83977fe3b6ef54c1d29c83b0a778d330f523441f.tar.gz
package/rpi-firmware/rpi-firmware.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -RPI_FIRMWARE_VERSION = 81cca1a9380c828299e884dba5efd0d4acb39e8d +RPI_FIRMWARE_VERSION = 83977fe3b6ef54c1d29c83b0a778d330f523441f RPI_FIRMWARE_SITE = $(call github,raspberrypi,firmware,$(RPI_FIRMWARE_VERSION)) RPI_FIRMWARE_LICENSE = BSD-3-Clause RPI_FIRMWARE_LICENSE_FILES = boot/LICENCE.broadcom
Signature · 1 line
2.20.1
PATCH 2/2 package/rpi-firmware: bump version to 83977fe3b6
Quoted 1 line · On Fri, 22 Feb 2019 23:37:04 +0100 Peter Seiderer <[email protected]> wrote:
Signed-off-by Peter Seiderer <[email protected]>
What is the reason for bumping to 83977fe3b6 in master ? And then to ebf7b40cdc in next ?
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
PATCH 2/2 package/rpi-firmware: bump version to 83977fe3b6
Hello Thomas,
Quoted 7 lines · Thomas Petazzoni
Quoted 1 line · On Fri, 22 Feb 2019 23:37:04 +0100 Peter Seiderer <[email protected]> wrote:
Signed-off-by Peter Seiderer <[email protected]>What is the reason for bumping to
83977fe3b6in master ? And then toebf7b40cdcin next ?
Sorry for the confusion, preparing the bump (maybe buildroot-master) to
- kernel 877656cd14 (4.14.98, up-to-date one from the 4.14 branch)
- firmware 83977fe3b6, last commit before [1]:
kernel bump to 4.19.23 See: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=224931
overlapped with the release of 4.19.23 [3] and the follow up bump (major kernel update for buildroot-next) to
- kernel 5eeff139ea (4.19.23)
- firmware ebf7b40cdc [2], one commit after [1],
Regards,
Peter
[1] https://github.com/raspberrypi/firmware/commit/d095b96ac33de9eb4b95539cb3261f35a3c74509
[2] https://github.com/raspberrypi/firmware/commit/ebf7b40cdc6effe7ffa3fd5195e8be01b94f80da
[3] https://www.phoronix.com/scan.php?page=news_item&px=Raspberry-Pi-Linux-4.19-Rolling
Quoted 2 lines
Thomas
PATCH 2/2 package/rpi-firmware: bump version to 83977fe3b6
Hello Peter,
Thanks for your feedback!
Quoted 11 lines · On Sat, 23 Feb 2019 15:27:11 +0100 Peter Seiderer <[email protected]> wrote:
Quoted 2 lines
What is the reason for bumping to
83977fe3b6in master ? And then toebf7b40cdcin next ?Sorry for the confusion, preparing the bump (maybe buildroot-master) to
- kernel
877656cd14(4.14.98, up-to-date one from the 4.14 branch)
- firmware83977fe3b6, last commit before [1]:kernel bump to 4.19.23 See: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=224931
What are the firmware changes between what's currently in master and 83977fe3b6 ? Does it make sense to apply this to master ?
Quoted 5 lines
overlapped with the release of 4.19.23 [3] and the follow up bump (major kernel update for buildroot-next) to
- kernel
5eeff139ea(4.19.23)
- firmwareebf7b40cdc[2], one commit after [1],
So the firmware version ebf7b40cdc is needed to boot a 4.19 kernel ? Is it backward compatible with the 4.14 kernel ?
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
PATCH 2/2 package/rpi-firmware: bump version to 83977fe3b6
Hello Thomas,
Quoted 15 lines · Thomas Petazzoni
Hello Peter,
Thanks for your feedback!
Quoted 8 lines · On Sat, 23 Feb 2019 15:27:11 +0100 Peter Seiderer <[email protected]> wrote:
Quoted 2 lines
What is the reason for bumping to
83977fe3b6in master ? And then toebf7b40cdcin next ?Sorry for the confusion, preparing the bump (maybe buildroot-master) to
- kernel
877656cd14(4.14.98, up-to-date one from the 4.14 branch)
- firmware83977fe3b6, last commit before [1]:
Quoted 6 lines
Quoted 3 lines
kernel bump to 4.19.23 See: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=224931What are the firmware changes between what's currently in master and
83977fe3b6? Does it make sense to apply this to master ?
Did not look at the (two) commits in detail, but I think as most firmware commits mention the specific kernel version it is the best to keep kernel/firmware in par?
The two commit logs are:
commit 83977fe3b6ef54c1d29c83b0a778d330f523441f
Author: popcornmix <[email protected]> Date: Tue Feb 12 21:36:56 2019 +0000
kernel: Bump to 4.14.98
kernel: balenaFin v1.1.0 carrier board update
See: https://github.com/raspberrypi/linux/pull/2852
kernel: configs: Enable the AD193x codecs
See: https://github.com/raspberrypi/linux/issues/2850
firmware: camera/image_encode: Add timestamp to frames encoded with image_encode
See: https://github.com/raspberrypi/linux/issues/2351
commit ea3841a7f916895a98da5c5972cca68baff8aac3
Author: popcornmix <[email protected]> Date: Tue Feb 5 14:10:03 2019 +0000
kernel: Bump to 4.14.97
kernel: audioinjector-octo: revert to dummy supplies
See: https://github.com/raspberrypi/linux/pull/2834Both do not only touch the binary kernel/module images but although overlay files and/or the boot files start/fixup...
Quoted 9 lines
Quoted 6 lines
overlapped with the release of 4.19.23 [3] and the follow up bump (major kernel update for buildroot-next) to
- kernel
5eeff139ea(4.19.23)
- firmwareebf7b40cdc[2], one commit after [1],So the firmware version
ebf7b40cdcis needed to boot a 4.19 kernel ? Is it backward compatible with the 4.14 kernel ?
Do not know (and hard to judge from the changed dtb binary blobs) and did not test it, but would like to keep kernel/firmware in par (see above)...
Regards,
Peter
Quoted 2 lines
Thomas
PATCH 1/2 configs/raspberrypi*: bump kernel version to 877656cd14
In reply to Peter SeidererQuoted 12 lines · On Fri, 22 Feb 2019 23:37:03 +0100 Peter Seiderer <[email protected]> wrote:
Now based on 4.14.98 (from 4.14.95)
Signed-off-by Peter Seiderer <[email protected]>--- configs/raspberrypi0_defconfig | 2 +- configs/raspberrypi0w_defconfig | 2 +- configs/raspberrypi2_defconfig | 2 +- configs/raspberrypi3_64_defconfig | 2 +- configs/raspberrypi3_defconfig | 2 +- configs/raspberrypi3_qt5we_defconfig | 2 +- configs/raspberrypi_defconfig | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-)
Both patches applied to master. Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com