From: Peter Seiderer <ps.report@gmx.net>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Martin Bark <martin@barkynet.com>,
Arthur Courtel <arthur.courtel@smile.fr>,
Vincent Fazio <vfazio@xes-inc.com>,
Mahyar Koshkouei <mahyar.koshkouei@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 2/4] package/rpi-firmware: bump version to 9f97081
Date: Wed, 6 Oct 2021 22:05:54 +0200 [thread overview]
Message-ID: <20211006220554.52f21e5e@gmx.net> (raw)
In-Reply-To: <16c55b45-955a-ef8f-9346-e5590c8b5a66@mind.be>
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
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-06 20:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 21:13 [Buildroot] [PATCH v1 1/4] configs/raspberrypi*: bump kernel version to 3e1698e (5.10.63) Peter Seiderer
2021-09-20 21:13 ` [Buildroot] [PATCH v1 2/4] package/rpi-firmware: bump version to 9f97081 Peter Seiderer
2021-09-20 21:19 ` Vincent Fazio
2021-09-20 21:41 ` Peter Seiderer
2021-09-21 13:08 ` Vincent Fazio
2021-09-21 20:39 ` Peter Seiderer
2021-09-23 13:58 ` Vincent Fazio
2021-09-30 19:19 ` Vincent Fazio
2021-09-30 19:54 ` Peter Seiderer
2021-10-06 18:24 ` Arnout Vandecappelle
2021-10-06 20:05 ` Peter Seiderer [this message]
2021-09-20 21:13 ` [Buildroot] [PATCH v1 3/4] package/rpi-bt-firmware: bump version to 883b726 Peter Seiderer
2021-09-20 21:13 ` [Buildroot] [PATCH v1 4/4] package/rpi-wifi-firmware: " Peter Seiderer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211006220554.52f21e5e@gmx.net \
--to=ps.report@gmx.net \
--cc=arnout@mind.be \
--cc=arthur.courtel@smile.fr \
--cc=buildroot@buildroot.org \
--cc=mahyar.koshkouei@gmail.com \
--cc=martin@barkynet.com \
--cc=vfazio@xes-inc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox