[2/2] package/rpi-firmware: bump version to 83977fe3b6
diff mbox series

Message ID 20190222223704.6202-2-ps.report@gmx.net
State Accepted
Headers show
Series
  • Untitled series #93775
Related show

Commit Message

Peter Seiderer Feb. 22, 2019, 10:37 p.m. UTC
Signed-off-by: Peter Seiderer <ps.report@gmx.net>
---
 package/rpi-firmware/rpi-firmware.hash | 2 +-
 package/rpi-firmware/rpi-firmware.mk   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

Comments

Thomas Petazzoni Feb. 23, 2019, 1:37 p.m. UTC | #1
On Fri, 22 Feb 2019 23:37:04 +0100
Peter Seiderer <ps.report@gmx.net> wrote:

> Signed-off-by: Peter Seiderer <ps.report@gmx.net>

What is the reason for bumping to 83977fe3b6 in master ? And then to
ebf7b40cdc in next ?

Thomas
Peter Seiderer Feb. 23, 2019, 2:27 p.m. UTC | #2
Hello Thomas,

On Sat, 23 Feb 2019 14:37:53 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> On Fri, 22 Feb 2019 23:37:04 +0100
> Peter Seiderer <ps.report@gmx.net> wrote:
> 
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>  
> 
> What is the reason for bumping to 83977fe3b6 in master ? And then to
> ebf7b40cdc in 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

> 
> Thomas
Thomas Petazzoni Feb. 23, 2019, 2:54 p.m. UTC | #3
Hello Peter,

Thanks for your feedback!

On Sat, 23 Feb 2019 15:27:11 +0100
Peter Seiderer <ps.report@gmx.net> wrote:

> > What is the reason for bumping to 83977fe3b6 in master ? And then to
> > ebf7b40cdc in 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

What are the firmware changes between what's currently in master and
83977fe3b6 ? Does it make sense to apply this to master ?

> 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],

So the firmware version ebf7b40cdc is needed to boot a 4.19 kernel ? Is
it backward compatible with the 4.14 kernel ?

Thomas
Peter Seiderer Feb. 23, 2019, 10:09 p.m. UTC | #4
Hello Thomas,

On Sat, 23 Feb 2019 15:54:37 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> Hello Peter,
> 
> Thanks for your feedback!
> 
> On Sat, 23 Feb 2019 15:27:11 +0100
> Peter Seiderer <ps.report@gmx.net> wrote:
> 
> > > What is the reason for bumping to 83977fe3b6 in master ? And then to
> > > ebf7b40cdc in 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  
> 
> What 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 <popcornmix@gmail.com>
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 <popcornmix@gmail.com>
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/2834


Both do not only touch the binary kernel/module images but although overlay
files and/or the boot files start/fixup...

> 
> > 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],  
> 
> So the firmware version ebf7b40cdc is 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

> 
> Thomas

Patch
diff mbox series

diff --git a/package/rpi-firmware/rpi-firmware.hash b/package/rpi-firmware/rpi-firmware.hash
index 9988dda717..b6b8824f3f 100644
--- a/package/rpi-firmware/rpi-firmware.hash
+++ b/package/rpi-firmware/rpi-firmware.hash
@@ -1,2 +1,2 @@ 
 # Locally computed
-sha256	f1d631920ed4ae15f368ba7b8b3caa4ed604f5223372cc6debbd39a101eb8d74  rpi-firmware-81cca1a9380c828299e884dba5efd0d4acb39e8d.tar.gz
+sha256 9a34ccc4a51695a33206cc6c8534f615ba5a30fcbce5fa3add400ecc6b80ad8a rpi-firmware-83977fe3b6ef54c1d29c83b0a778d330f523441f.tar.gz
diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk
index e41b3442e6..b883e9d989 100644
--- a/package/rpi-firmware/rpi-firmware.mk
+++ b/package/rpi-firmware/rpi-firmware.mk
@@ -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