From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Fri, 14 Apr 2023 18:34:43 +0200 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pnMNm-003UQ4-HL for lore@lore.pengutronix.de; Fri, 14 Apr 2023 18:34:43 +0200 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1pnMNl-0006or-Li; Fri, 14 Apr 2023 18:34:41 +0200 Received: from drehscheibe.grey.stw.pengutronix.de ([2a0a:edc0:0:c01:1d::a2]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pnMNb-0006oc-A5; Fri, 14 Apr 2023 18:34:31 +0200 Received: from [2a0a:edc0:0:1101:1d::54] (helo=dude05.red.stw.pengutronix.de) by drehscheibe.grey.stw.pengutronix.de with esmtp (Exim 4.94.2) (envelope-from ) id 1pnMNa-00BEw6-LW; Fri, 14 Apr 2023 18:34:30 +0200 Received: from afa by dude05.red.stw.pengutronix.de with local (Exim 4.94.2) (envelope-from ) id 1pnMNa-002XHz-3d; Fri, 14 Apr 2023 18:34:30 +0200 From: Ahmad Fatoum To: distrokit@pengutronix.de Date: Fri, 14 Apr 2023 18:34:29 +0200 Message-Id: <20230414163429.602101-1-a.fatoum@pengutronix.de> X-Mailer: git-send-email 2.39.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [DistroKit] [PATCH] v8a: barebox: rockchip: disable CONFIG_MMCBLKDEV_ROOTARG X-BeenThere: distrokit@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: DistroKit Mailinglist List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Ahmad Fatoum Sender: "DistroKit" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: distrokit-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false 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 --- This is required to boot currently used kernel with barebox-next. --- configs/platform-v8a/barebox-rockchip.config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configs/platform-v8a/barebox-rockchip.config b/configs/platform-v8a/barebox-rockchip.config index 109f55c12aba..c063a97b6de9 100644 --- a/configs/platform-v8a/barebox-rockchip.config +++ b/configs/platform-v8a/barebox-rockchip.config @@ -179,7 +179,7 @@ CONFIG_BOOTM_OFTREE=y # CONFIG_BOOTM_FITIMAGE is not set CONFIG_BLSPEC=y CONFIG_FLEXIBLE_BOOTARGS=y -CONFIG_MMCBLKDEV_ROOTARG=y +# CONFIG_MMCBLKDEV_ROOTARG is not set CONFIG_BAREBOX_UPDATE=y CONFIG_SYSTEM_PARTITIONS=y CONFIG_IMD=y -- 2.39.2