From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH] v8a: barebox: rockchip: disable CONFIG_MMCBLKDEV_ROOTARG
Date: Fri, 14 Apr 2023 18:45:05 +0200 [thread overview]
Message-ID: <ZDmDEf0q9J2RhTL0@pengutronix.de> (raw)
In-Reply-To: <20230414163429.602101-1-a.fatoum@pengutronix.de>
On Fri, Apr 14, 2023 at 06:34:29PM +0200, Ahmad Fatoum wrote:
> The help text of CONFIG_MMCBLKDEV_ROOTARG is pretty clear on that the
> option should only be used when barebox and kernel aliases agree.
> The upstream kernel DT aliases for all Radxa boards were recently
> changed, so depending on whether we update kernel or barebox first,
> we may experience breakage. Let's avoid this by using the default
> PARTUUID-based root argument generation again until we have updated
> both barebox and Linux to device tree revisions that agree.
>
> [afa: It would be best if barebox' append_root feature could just
> use kernel aliases, but this is not totally trivial, as the root=
> entry is generated early at barebox mount time and kernel DT
> isn't known till boot]
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> This is required to boot currently used kernel with barebox-next.
Applied to next.
rsc
--
Pengutronix e.K. | Dipl.-Ing. Robert Schwebel |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
prev parent reply other threads:[~2023-04-14 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 16:34 Ahmad Fatoum
2023-04-14 16:45 ` Robert Schwebel [this message]
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=ZDmDEf0q9J2RhTL0@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=distrokit@pengutronix.de \
/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