diff mbox series

[v1,2/4] package/rpi-firmware: bump version to 9f97081

Message ID 20210920211328.17526-2-ps.report@gmx.net
State Changes Requested
Headers show
Series [v1,1/4] configs/raspberrypi*: bump kernel version to 3e1698e (5.10.63) | expand

Commit Message

Peter Seiderer Sept. 20, 2021, 9:13 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

Vincent Fazio Sept. 20, 2021, 9:19 p.m. UTC | #1
Peter,

On 9/20/21 4:13 PM, Peter Seiderer wrote:
> 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(-)
>
> diff --git a/package/rpi-firmware/rpi-firmware.hash b/package/rpi-firmware/rpi-firmware.hash
> index 7127b2d824..d6243cb54c 100644
> --- a/package/rpi-firmware/rpi-firmware.hash
> +++ b/package/rpi-firmware/rpi-firmware.hash
> @@ -1,3 +1,3 @@
>   # Locally computed
> -sha256  5eaff5da660d6ecd74bb2c927d7a1ba84b5e5c5582f02e65aec058af2ffe50f4  rpi-firmware-33e09977ff3b02967d191801e3361224455acb9d.tar.gz
> +sha256  60be376238b08b928f98a25ecf90172067c17ad1db543d813409ee6c54b13b07  rpi-firmware-9f9708199f8809ecf16119d0716375bee7b7d8d4.tar.gz
>   sha256  c7283ff51f863d93a275c66e3b4cb08021a5dd4d8c1e7acc47d872fbe52d3d6b  boot/LICENCE.broadcom
> diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk
> index 181650fa08..6a2bf05248 100644
> --- a/package/rpi-firmware/rpi-firmware.mk
> +++ b/package/rpi-firmware/rpi-firmware.mk
> @@ -4,7 +4,7 @@
>   #
>   ################################################################################
>   
> -RPI_FIRMWARE_VERSION = 33e09977ff3b02967d191801e3361224455acb9d
> +RPI_FIRMWARE_VERSION = 9f9708199f8809ecf16119d0716375bee7b7d8d4
There is a regression introduced with 
https://github.com/raspberrypi/firmware/commit/25e2b597ebfb2495eab4816a276758dcc6ea21f1
See here: https://github.com/raspberrypi/firmware/issues/1619
>   RPI_FIRMWARE_SITE = $(call github,raspberrypi,firmware,$(RPI_FIRMWARE_VERSION))
>   RPI_FIRMWARE_LICENSE = BSD-3-Clause
>   RPI_FIRMWARE_LICENSE_FILES = boot/LICENCE.broadcom
Peter Seiderer Sept. 20, 2021, 9:41 p.m. UTC | #2
Hello Vincent,

On Mon, 20 Sep 2021 16:19:57 -0500, Vincent Fazio <vfazio@xes-inc.com> wrote:

> Peter,
>
> On 9/20/21 4:13 PM, Peter Seiderer wrote:
> > 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(-)
> >
> > diff --git a/package/rpi-firmware/rpi-firmware.hash b/package/rpi-firmware/rpi-firmware.hash
> > index 7127b2d824..d6243cb54c 100644
> > --- a/package/rpi-firmware/rpi-firmware.hash
> > +++ b/package/rpi-firmware/rpi-firmware.hash
> > @@ -1,3 +1,3 @@
> >   # Locally computed
> > -sha256  5eaff5da660d6ecd74bb2c927d7a1ba84b5e5c5582f02e65aec058af2ffe50f4  rpi-firmware-33e09977ff3b02967d191801e3361224455acb9d.tar.gz
> > +sha256  60be376238b08b928f98a25ecf90172067c17ad1db543d813409ee6c54b13b07  rpi-firmware-9f9708199f8809ecf16119d0716375bee7b7d8d4.tar.gz
> >   sha256  c7283ff51f863d93a275c66e3b4cb08021a5dd4d8c1e7acc47d872fbe52d3d6b  boot/LICENCE.broadcom
> > diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk
> > index 181650fa08..6a2bf05248 100644
> > --- a/package/rpi-firmware/rpi-firmware.mk
> > +++ b/package/rpi-firmware/rpi-firmware.mk
> > @@ -4,7 +4,7 @@
> >   #
> >   ################################################################################
> >
> > -RPI_FIRMWARE_VERSION = 33e09977ff3b02967d191801e3361224455acb9d
> > +RPI_FIRMWARE_VERSION = 9f9708199f8809ecf16119d0716375bee7b7d8d4
>
> There is a regression introduced with
> https://github.com/raspberrypi/firmware/commit/25e2b597ebfb2495eab4816a276758dcc6ea21f1
> See here: https://github.com/raspberrypi/firmware/issues/1619
>

Thanks for the info, only did a quick read of the PR 1619, the problem
seems U-boot specific (not the buildroot default case) and there is
already a suggested U-boot fix (submitted by you)?

Regards,
Peter


> >   RPI_FIRMWARE_SITE = $(call github,raspberrypi,firmware,$(RPI_FIRMWARE_VERSION))
> >   RPI_FIRMWARE_LICENSE = BSD-3-Clause
> >   RPI_FIRMWARE_LICENSE_FILES = boot/LICENCE.broadcom
>
Vincent Fazio Sept. 21, 2021, 1:08 p.m. UTC | #3
Peter, all,

On 9/20/21 4:41 PM, Peter Seiderer wrote:
> Hello Vincent,
>
> On Mon, 20 Sep 2021 16:19:57 -0500, Vincent Fazio <vfazio@xes-inc.com> wrote:
>
>> Peter,
>>
>> On 9/20/21 4:13 PM, Peter Seiderer wrote:
>>> 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(-)
>>>
>>> diff --git a/package/rpi-firmware/rpi-firmware.hash b/package/rpi-firmware/rpi-firmware.hash
>>> index 7127b2d824..d6243cb54c 100644
>>> --- a/package/rpi-firmware/rpi-firmware.hash
>>> +++ b/package/rpi-firmware/rpi-firmware.hash
>>> @@ -1,3 +1,3 @@
>>>    # Locally computed
>>> -sha256  5eaff5da660d6ecd74bb2c927d7a1ba84b5e5c5582f02e65aec058af2ffe50f4  rpi-firmware-33e09977ff3b02967d191801e3361224455acb9d.tar.gz
>>> +sha256  60be376238b08b928f98a25ecf90172067c17ad1db543d813409ee6c54b13b07  rpi-firmware-9f9708199f8809ecf16119d0716375bee7b7d8d4.tar.gz
>>>    sha256  c7283ff51f863d93a275c66e3b4cb08021a5dd4d8c1e7acc47d872fbe52d3d6b  boot/LICENCE.broadcom
>>> diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk
>>> index 181650fa08..6a2bf05248 100644
>>> --- a/package/rpi-firmware/rpi-firmware.mk
>>> +++ b/package/rpi-firmware/rpi-firmware.mk
>>> @@ -4,7 +4,7 @@
>>>    #
>>>    ################################################################################
>>>
>>> -RPI_FIRMWARE_VERSION = 33e09977ff3b02967d191801e3361224455acb9d
>>> +RPI_FIRMWARE_VERSION = 9f9708199f8809ecf16119d0716375bee7b7d8d4
>> There is a regression introduced with
>> https://github.com/raspberrypi/firmware/commit/25e2b597ebfb2495eab4816a276758dcc6ea21f1
>> See here: https://github.com/raspberrypi/firmware/issues/1619
>>
> Thanks for the info, only did a quick read of the PR 1619, the problem
> seems U-boot specific (not the buildroot default case) and there is
> already a suggested U-boot fix (submitted by you)?

Yes, sorry I was not very clear in my email yesterday (I was sending it 
on my way out the door).

Yes, u-boot is affected, though I think edk2 may also be affected. The 
u-boot patch has not yet been reviewed and may not make it for 2021.10

I just wanted to give a heads up that bumping this package could have 
consequences for some configurations.

> Regards,
> Peter
>
>
>>>    RPI_FIRMWARE_SITE = $(call github,raspberrypi,firmware,$(RPI_FIRMWARE_VERSION))
>>>    RPI_FIRMWARE_LICENSE = BSD-3-Clause
>>>    RPI_FIRMWARE_LICENSE_FILES = boot/LICENCE.broadcom
Peter Seiderer Sept. 21, 2021, 8:39 p.m. UTC | #4
Hello Vincent, all,

On Tue, 21 Sep 2021 08:08:10 -0500, Vincent Fazio <vfazio@xes-inc.com> wrote:

> Peter, all,
>
> On 9/20/21 4:41 PM, Peter Seiderer wrote:
> > Hello Vincent,
> >
> > On Mon, 20 Sep 2021 16:19:57 -0500, Vincent Fazio <vfazio@xes-inc.com> wrote:
> >
> >> Peter,
> >>
> >> On 9/20/21 4:13 PM, Peter Seiderer wrote:
> >>> 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(-)
> >>>
> >>> diff --git a/package/rpi-firmware/rpi-firmware.hash b/package/rpi-firmware/rpi-firmware.hash
> >>> index 7127b2d824..d6243cb54c 100644
> >>> --- a/package/rpi-firmware/rpi-firmware.hash
> >>> +++ b/package/rpi-firmware/rpi-firmware.hash
> >>> @@ -1,3 +1,3 @@
> >>>    # Locally computed
> >>> -sha256  5eaff5da660d6ecd74bb2c927d7a1ba84b5e5c5582f02e65aec058af2ffe50f4  rpi-firmware-33e09977ff3b02967d191801e3361224455acb9d.tar.gz
> >>> +sha256  60be376238b08b928f98a25ecf90172067c17ad1db543d813409ee6c54b13b07  rpi-firmware-9f9708199f8809ecf16119d0716375bee7b7d8d4.tar.gz
> >>>    sha256  c7283ff51f863d93a275c66e3b4cb08021a5dd4d8c1e7acc47d872fbe52d3d6b  boot/LICENCE.broadcom
> >>> diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk
> >>> index 181650fa08..6a2bf05248 100644
> >>> --- a/package/rpi-firmware/rpi-firmware.mk
> >>> +++ b/package/rpi-firmware/rpi-firmware.mk
> >>> @@ -4,7 +4,7 @@
> >>>    #
> >>>    ################################################################################
> >>>
> >>> -RPI_FIRMWARE_VERSION = 33e09977ff3b02967d191801e3361224455acb9d
> >>> +RPI_FIRMWARE_VERSION = 9f9708199f8809ecf16119d0716375bee7b7d8d4
> >> There is a regression introduced with
> >> https://github.com/raspberrypi/firmware/commit/25e2b597ebfb2495eab4816a276758dcc6ea21f1
> >> See here: https://github.com/raspberrypi/firmware/issues/1619
> >>
> > Thanks for the info, only did a quick read of the PR 1619, the problem
> > seems U-boot specific (not the buildroot default case) and there is
> > already a suggested U-boot fix (submitted by you)?
>
> Yes, sorry I was not very clear in my email yesterday (I was sending it
> on my way out the door).

No problem ;-), the hint was/is very valuable!

>
> Yes, u-boot is affected, though I think edk2 may also be affected. The
> u-boot patch has not yet been reviewed and may not make it for 2021.10
>
> I just wanted to give a heads up that bumping this package could have
> consequences for some configurations.

So there are the following possibilities:

- never update rpi-firmware to not break legacy u-boot (and maybe edk2 and
  maybe linux-mainline and maybe ...) setups

- delay the rpi-firmware update until up-to-date u-boot (and edk2 and ...)
  are available (as this bump seems to fix some other regressions e.g
  'kernel: Second attempt to fix the CPU startup failure' [1]

- apply the rpi-firmware update now and hope that this email thread is
  found by all people affected by the u-boot (and ...) defect, but
  keeps the default buildroot/rpi users up-to-date ;-)

Regards,
Peter

[1] https://github.com/raspberrypi/firmware/commit/9f9708199f8809ecf16119d0716375bee7b7d8d4

>
> > Regards,
> > Peter
> >
> >
> >>>    RPI_FIRMWARE_SITE = $(call github,raspberrypi,firmware,$(RPI_FIRMWARE_VERSION))
> >>>    RPI_FIRMWARE_LICENSE = BSD-3-Clause
> >>>    RPI_FIRMWARE_LICENSE_FILES = boot/LICENCE.broadcom
>
Vincent Fazio Sept. 23, 2021, 1:58 p.m. UTC | #5
All,

On 9/21/21 3:39 PM, Peter Seiderer wrote:
> Hello Vincent, all,
>
> On Tue, 21 Sep 2021 08:08:10 -0500, Vincent Fazio <vfazio@xes-inc.com> wrote:
>
>> Peter, all,
>>
>> On 9/20/21 4:41 PM, Peter Seiderer wrote:
>>> Hello Vincent,
>>>
>>> On Mon, 20 Sep 2021 16:19:57 -0500, Vincent Fazio <vfazio@xes-inc.com> wrote:
>>>
>>> Thanks for the info, only did a quick read of the PR 1619, the problem
>>> seems U-boot specific (not the buildroot default case) and there is
>>> already a suggested U-boot fix (submitted by you)?
>> Yes, sorry I was not very clear in my email yesterday (I was sending it
>> on my way out the door).
> No problem ;-), the hint was/is very valuable!
>
>> Yes, u-boot is affected, though I think edk2 may also be affected. The
>> u-boot patch has not yet been reviewed and may not make it for 2021.10
>>
>> I just wanted to give a heads up that bumping this package could have
>> consequences for some configurations.
> So there are the following possibilities:
>
> - never update rpi-firmware to not break legacy u-boot (and maybe edk2 and
>    maybe linux-mainline and maybe ...) setups
Definitely not recommending this.
> - delay the rpi-firmware update until up-to-date u-boot (and edk2 and ...)
>    are available (as this bump seems to fix some other regressions e.g
>    'kernel: Second attempt to fix the CPU startup failure' [1]
>
> - apply the rpi-firmware update now and hope that this email thread is
>    found by all people affected by the u-boot (and ...) defect, but
>    keeps the default buildroot/rpi users up-to-date ;-)

Probably no reason to delay it if there are no default configurations 
that utilize the affected packages, but not sure if it deserves a 
mention somewhere like 
https://buildroot.org/downloads/manual/manual.html#_known_issues so the 
issue is more clearly advertised until there are patches to fix the 
affected packages.

I'll let the maintainers decide what to do. Again, I just wanted to make 
people aware.

> Regards,
> Peter
>
> [1] https://github.com/raspberrypi/firmware/commit/9f9708199f8809ecf16119d0716375bee7b7d8d4
>
>>> Regards,
>>> Peter
>>>
>>>
Vincent Fazio Sept. 30, 2021, 7:19 p.m. UTC | #6
Peter, all,

On 9/23/21 8:58 AM, Vincent Fazio wrote:
> All,
>
> On 9/21/21 3:39 PM, Peter Seiderer wrote:
>> Hello Vincent, all,
>>
>> On Tue, 21 Sep 2021 08:08:10 -0500, Vincent Fazio 
>> <vfazio@xes-inc.com> wrote:
>>
>>> Peter, all,
>>>
>>> On 9/20/21 4:41 PM, Peter Seiderer wrote:
>>>> Hello Vincent,
>>>>
>>>> On Mon, 20 Sep 2021 16:19:57 -0500, Vincent Fazio 
>>>> <vfazio@xes-inc.com> wrote:
>>>>
>>>> Thanks for the info, only did a quick read of the PR 1619, the problem
>>>> seems U-boot specific (not the buildroot default case) and there is
>>>> already a suggested U-boot fix (submitted by you)?
>>> Yes, sorry I was not very clear in my email yesterday (I was sending it
>>> on my way out the door).
>> No problem ;-), the hint was/is very valuable!
This may no longer be an issue other packages have to deal with [1]
>>
>>> Yes, u-boot is affected, though I think edk2 may also be affected. The
>>> u-boot patch has not yet been reviewed and may not make it for 2021.10
>>>
>>> I just wanted to give a heads up that bumping this package could have
>>> consequences for some configurations.
>> So there are the following possibilities:
>>
>> - never update rpi-firmware to not break legacy u-boot (and maybe 
>> edk2 and
>>    maybe linux-mainline and maybe ...) setups
> Definitely not recommending this.
>> - delay the rpi-firmware update until up-to-date u-boot (and edk2 and 
>> ...)
>>    are available (as this bump seems to fix some other regressions e.g
>>    'kernel: Second attempt to fix the CPU startup failure' [1]
>>
>> - apply the rpi-firmware update now and hope that this email thread is
>>    found by all people affected by the u-boot (and ...) defect, but
>>    keeps the default buildroot/rpi users up-to-date ;-)
>
> Probably no reason to delay it if there are no default configurations 
> that utilize the affected packages, but not sure if it deserves a 
> mention somewhere like 
> https://buildroot.org/downloads/manual/manual.html#_known_issues so 
> the issue is more clearly advertised until there are patches to fix 
> the affected packages.
>
> I'll let the maintainers decide what to do. Again, I just wanted to 
> make people aware.
>
>> Regards,
>> Peter
>>
>> [1] 
>> https://github.com/raspberrypi/firmware/commit/9f9708199f8809ecf16119d0716375bee7b7d8d4
>>
>>>> Regards,
>>>> Peter
>>>>
>>>>
[1] 
https://github.com/raspberrypi/firmware/commit/b5257da58c0e652633592c6fce09a7f3b100a2eb
Peter Seiderer Sept. 30, 2021, 7:54 p.m. UTC | #7
Hello Vincent, all,

On Thu, 30 Sep 2021 14:19:03 -0500, Vincent Fazio <vfazio@xes-inc.com> wrote:

> Peter, all,
> 
> On 9/23/21 8:58 AM, Vincent Fazio wrote:
> > All,
> >
> > On 9/21/21 3:39 PM, Peter Seiderer wrote:  
> >> Hello Vincent, all,
> >>
> >> On Tue, 21 Sep 2021 08:08:10 -0500, Vincent Fazio 
> >> <vfazio@xes-inc.com> wrote:
> >>  
> >>> Peter, all,
> >>>
> >>> On 9/20/21 4:41 PM, Peter Seiderer wrote:  
> >>>> Hello Vincent,
> >>>>
> >>>> On Mon, 20 Sep 2021 16:19:57 -0500, Vincent Fazio 
> >>>> <vfazio@xes-inc.com> wrote:
> >>>>
> >>>> Thanks for the info, only did a quick read of the PR 1619, the problem
> >>>> seems U-boot specific (not the buildroot default case) and there is
> >>>> already a suggested U-boot fix (submitted by you)?  
> >>> Yes, sorry I was not very clear in my email yesterday (I was sending it
> >>> on my way out the door).  
> >> No problem ;-), the hint was/is very valuable!  
>
> This may no longer be an issue other packages have to deal with [1]
>

Thanks for update (and your debugging efforts ;-) ), will update my
patchset the next days...

Regards,
Peter

> >>  
> >>> Yes, u-boot is affected, though I think edk2 may also be affected. The
> >>> u-boot patch has not yet been reviewed and may not make it for 2021.10
> >>>
> >>> I just wanted to give a heads up that bumping this package could have
> >>> consequences for some configurations.  
> >> So there are the following possibilities:
> >>
> >> - never update rpi-firmware to not break legacy u-boot (and maybe 
> >> edk2 and
> >>    maybe linux-mainline and maybe ...) setups  
> > Definitely not recommending this.  
> >> - delay the rpi-firmware update until up-to-date u-boot (and edk2 and 
> >> ...)
> >>    are available (as this bump seems to fix some other regressions e.g
> >>    'kernel: Second attempt to fix the CPU startup failure' [1]
> >>
> >> - apply the rpi-firmware update now and hope that this email thread is
> >>    found by all people affected by the u-boot (and ...) defect, but
> >>    keeps the default buildroot/rpi users up-to-date ;-)  
> >
> > Probably no reason to delay it if there are no default configurations 
> > that utilize the affected packages, but not sure if it deserves a 
> > mention somewhere like 
> > https://buildroot.org/downloads/manual/manual.html#_known_issues so 
> > the issue is more clearly advertised until there are patches to fix 
> > the affected packages.
> >
> > I'll let the maintainers decide what to do. Again, I just wanted to 
> > make people aware.
> >  
> >> Regards,
> >> Peter
> >>
> >> [1] 
> >> https://github.com/raspberrypi/firmware/commit/9f9708199f8809ecf16119d0716375bee7b7d8d4
> >>  
> >>>> Regards,
> >>>> Peter
> >>>>
> >>>>  
> [1] 
> https://github.com/raspberrypi/firmware/commit/b5257da58c0e652633592c6fce09a7f3b100a2eb
>
Arnout Vandecappelle Oct. 6, 2021, 6:24 p.m. UTC | #8
On 30/09/2021 21:54, Peter Seiderer wrote:
> Hello Vincent, all,
> 
> On Thu, 30 Sep 2021 14:19:03 -0500, Vincent Fazio <vfazio@xes-inc.com> wrote:
> 
>> Peter, all,
>>
>> On 9/23/21 8:58 AM, Vincent Fazio wrote:
>>> All,
>>>
>>> On 9/21/21 3:39 PM, Peter Seiderer wrote:
>>>> Hello Vincent, all,
>>>>
>>>> On Tue, 21 Sep 2021 08:08:10 -0500, Vincent Fazio
>>>> <vfazio@xes-inc.com> wrote:
>>>>   
>>>>> Peter, all,
>>>>>
>>>>> On 9/20/21 4:41 PM, Peter Seiderer wrote:
>>>>>> Hello Vincent,
>>>>>>
>>>>>> On Mon, 20 Sep 2021 16:19:57 -0500, Vincent Fazio
>>>>>> <vfazio@xes-inc.com> wrote:
>>>>>>
>>>>>> Thanks for the info, only did a quick read of the PR 1619, the problem
>>>>>> seems U-boot specific (not the buildroot default case) and there is
>>>>>> already a suggested U-boot fix (submitted by you)?
>>>>> Yes, sorry I was not very clear in my email yesterday (I was sending it
>>>>> on my way out the door).
>>>> No problem ;-), the hint was/is very valuable!
>>
>> This may no longer be an issue other packages have to deal with [1]
>>
> 
> Thanks for update (and your debugging efforts ;-) ), will update my
> patchset the next days...

  I was going to apply this series and then I saw this comment... Are you still 
going to update the patchset or should we apply as-is?

  Regards,
  Arnout

> 
> Regards,
> Peter
> 
>>>>   
>>>>> Yes, u-boot is affected, though I think edk2 may also be affected. The
>>>>> u-boot patch has not yet been reviewed and may not make it for 2021.10
>>>>>
>>>>> I just wanted to give a heads up that bumping this package could have
>>>>> consequences for some configurations.
>>>> So there are the following possibilities:
>>>>
>>>> - never update rpi-firmware to not break legacy u-boot (and maybe
>>>> edk2 and
>>>>     maybe linux-mainline and maybe ...) setups
>>> Definitely not recommending this.
>>>> - delay the rpi-firmware update until up-to-date u-boot (and edk2 and
>>>> ...)
>>>>     are available (as this bump seems to fix some other regressions e.g
>>>>     'kernel: Second attempt to fix the CPU startup failure' [1]
>>>>
>>>> - apply the rpi-firmware update now and hope that this email thread is
>>>>     found by all people affected by the u-boot (and ...) defect, but
>>>>     keeps the default buildroot/rpi users up-to-date ;-)
>>>
>>> Probably no reason to delay it if there are no default configurations
>>> that utilize the affected packages, but not sure if it deserves a
>>> mention somewhere like
>>> https://buildroot.org/downloads/manual/manual.html#_known_issues so
>>> the issue is more clearly advertised until there are patches to fix
>>> the affected packages.
>>>
>>> I'll let the maintainers decide what to do. Again, I just wanted to
>>> make people aware.
>>>   
>>>> Regards,
>>>> Peter
>>>>
>>>> [1]
>>>> https://github.com/raspberrypi/firmware/commit/9f9708199f8809ecf16119d0716375bee7b7d8d4
>>>>   
>>>>>> Regards,
>>>>>> Peter
>>>>>>
>>>>>>   
>> [1]
>> https://github.com/raspberrypi/firmware/commit/b5257da58c0e652633592c6fce09a7f3b100a2eb
>>
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
>
Peter Seiderer Oct. 6, 2021, 8:05 p.m. UTC | #9
Hello Arnout,

On Wed, 6 Oct 2021 20:24:44 +0200, Arnout Vandecappelle <arnout@mind.be> wrote:

> On 30/09/2021 21:54, Peter Seiderer wrote:
> > Hello Vincent, all,
> > 
> > On Thu, 30 Sep 2021 14:19:03 -0500, Vincent Fazio <vfazio@xes-inc.com> wrote:
> >   
> >> Peter, all,
> >>
> >> On 9/23/21 8:58 AM, Vincent Fazio wrote:  
> >>> All,
> >>>
> >>> On 9/21/21 3:39 PM, Peter Seiderer wrote:  
> >>>> Hello Vincent, all,
> >>>>
> >>>> On Tue, 21 Sep 2021 08:08:10 -0500, Vincent Fazio
> >>>> <vfazio@xes-inc.com> wrote:
> >>>>     
> >>>>> Peter, all,
> >>>>>
> >>>>> On 9/20/21 4:41 PM, Peter Seiderer wrote:  
> >>>>>> Hello Vincent,
> >>>>>>
> >>>>>> On Mon, 20 Sep 2021 16:19:57 -0500, Vincent Fazio
> >>>>>> <vfazio@xes-inc.com> wrote:
> >>>>>>
> >>>>>> Thanks for the info, only did a quick read of the PR 1619, the problem
> >>>>>> seems U-boot specific (not the buildroot default case) and there is
> >>>>>> already a suggested U-boot fix (submitted by you)?  
> >>>>> Yes, sorry I was not very clear in my email yesterday (I was sending it
> >>>>> on my way out the door).  
> >>>> No problem ;-), the hint was/is very valuable!  
> >>
> >> This may no longer be an issue other packages have to deal with [1]
> >>  
> > 
> > Thanks for update (and your debugging efforts ;-) ), will update my
> > patchset the next days...  
> 
>   I was going to apply this series and then I saw this comment... Are you still 
> going to update the patchset or should we apply as-is?

Still planing to update (but need to find a large enough time slot for testing,
but will finish hopefully until end of the week)...

Regards,
Peter

> 
>   Regards,
>   Arnout
> 
> > 
> > Regards,
> > Peter
> >   
> >>>>     
> >>>>> Yes, u-boot is affected, though I think edk2 may also be affected. The
> >>>>> u-boot patch has not yet been reviewed and may not make it for 2021.10
> >>>>>
> >>>>> I just wanted to give a heads up that bumping this package could have
> >>>>> consequences for some configurations.  
> >>>> So there are the following possibilities:
> >>>>
> >>>> - never update rpi-firmware to not break legacy u-boot (and maybe
> >>>> edk2 and
> >>>>     maybe linux-mainline and maybe ...) setups  
> >>> Definitely not recommending this.  
> >>>> - delay the rpi-firmware update until up-to-date u-boot (and edk2 and
> >>>> ...)
> >>>>     are available (as this bump seems to fix some other regressions e.g
> >>>>     'kernel: Second attempt to fix the CPU startup failure' [1]
> >>>>
> >>>> - apply the rpi-firmware update now and hope that this email thread is
> >>>>     found by all people affected by the u-boot (and ...) defect, but
> >>>>     keeps the default buildroot/rpi users up-to-date ;-)  
> >>>
> >>> Probably no reason to delay it if there are no default configurations
> >>> that utilize the affected packages, but not sure if it deserves a
> >>> mention somewhere like
> >>> https://buildroot.org/downloads/manual/manual.html#_known_issues so
> >>> the issue is more clearly advertised until there are patches to fix
> >>> the affected packages.
> >>>
> >>> I'll let the maintainers decide what to do. Again, I just wanted to
> >>> make people aware.
> >>>     
> >>>> Regards,
> >>>> Peter
> >>>>
> >>>> [1]
> >>>> https://github.com/raspberrypi/firmware/commit/9f9708199f8809ecf16119d0716375bee7b7d8d4
> >>>>     
> >>>>>> Regards,
> >>>>>> Peter
> >>>>>>
> >>>>>>     
> >> [1]
> >> https://github.com/raspberrypi/firmware/commit/b5257da58c0e652633592c6fce09a7f3b100a2eb
> >>  
> > 
> > _______________________________________________
> > buildroot mailing list
> > buildroot@buildroot.org
> > https://lists.buildroot.org/mailman/listinfo/buildroot
> >   
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
diff mbox series

Patch

diff --git a/package/rpi-firmware/rpi-firmware.hash b/package/rpi-firmware/rpi-firmware.hash
index 7127b2d824..d6243cb54c 100644
--- a/package/rpi-firmware/rpi-firmware.hash
+++ b/package/rpi-firmware/rpi-firmware.hash
@@ -1,3 +1,3 @@ 
 # Locally computed
-sha256  5eaff5da660d6ecd74bb2c927d7a1ba84b5e5c5582f02e65aec058af2ffe50f4  rpi-firmware-33e09977ff3b02967d191801e3361224455acb9d.tar.gz
+sha256  60be376238b08b928f98a25ecf90172067c17ad1db543d813409ee6c54b13b07  rpi-firmware-9f9708199f8809ecf16119d0716375bee7b7d8d4.tar.gz
 sha256  c7283ff51f863d93a275c66e3b4cb08021a5dd4d8c1e7acc47d872fbe52d3d6b  boot/LICENCE.broadcom
diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk
index 181650fa08..6a2bf05248 100644
--- a/package/rpi-firmware/rpi-firmware.mk
+++ b/package/rpi-firmware/rpi-firmware.mk
@@ -4,7 +4,7 @@ 
 #
 ################################################################################
 
-RPI_FIRMWARE_VERSION = 33e09977ff3b02967d191801e3361224455acb9d
+RPI_FIRMWARE_VERSION = 9f9708199f8809ecf16119d0716375bee7b7d8d4
 RPI_FIRMWARE_SITE = $(call github,raspberrypi,firmware,$(RPI_FIRMWARE_VERSION))
 RPI_FIRMWARE_LICENSE = BSD-3-Clause
 RPI_FIRMWARE_LICENSE_FILES = boot/LICENCE.broadcom