From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Wed, 11 Feb 2026 13:54:03 +0100 Received: from metis.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::104]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vq9jG-000XFT-2o for lore@lore.pengutronix.de; Wed, 11 Feb 2026 13:54:03 +0100 Received: from bombadil.infradead.org ([2607:7c80:54:3::133]) by metis.whiteo.stw.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1vq9jH-0002Sv-3M for lore@pengutronix.de; Wed, 11 Feb 2026 13:54:03 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=KrhdXI4zds17hWYJ5Wgml7a9mrDf6H660G5FwCL0XdA=; b=slaiTaKS4YmQsN4B/7vZLCt+GJ hFn9rnpkRDUvKVYhTtWD5iSS5bJVhbz6qaVwQSitq3M7quvivIW5PM0CE7nSkmadb6O8wmhfSeiiO Yd8UAeMZbUpFW19UCNoZAZpa1CNBXnnbhcDtDnp5jjGBTPjJUZqbruAdQnbdvjfX9+zSl0ZdlnMOU q+SoGVSfe7jqBMtv2LOvAPV1sx3FRQwlUe93WLj5W94q1K40NfltNqPtsVFZYGUu+YvI4QNmt00Cn 4A9/hxNLnwg3pwhE7WK8mv6GRQ8Dp2FUuZ/dHJqA4deTtKl4DrpoZnMJwG8RYGK8xh+umNFPNDMVx +f+rtO1w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1vq9ib-00000000eFh-3jzj; Wed, 11 Feb 2026 12:53:21 +0000 Received: from metis.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::104]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1vq9iY-00000000eEN-3Wh3 for barebox@lists.infradead.org; Wed, 11 Feb 2026 12:53:20 +0000 Received: from drehscheibe.grey.stw.pengutronix.de ([2a0a:edc0:0:c01:1d::a2]) by metis.whiteo.stw.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1vq9iX-0002L8-1J; Wed, 11 Feb 2026 13:53:17 +0100 Received: from pty.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::c5]) by drehscheibe.grey.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vq9iV-000FIX-1P; Wed, 11 Feb 2026 13:53:16 +0100 Received: from sha by pty.whiteo.stw.pengutronix.de with local (Exim 4.96) (envelope-from ) id 1vq9iW-00Bt1u-2B; Wed, 11 Feb 2026 13:53:16 +0100 Date: Wed, 11 Feb 2026 13:53:16 +0100 From: Sascha Hauer To: Marco Felsch Cc: Ahmad Fatoum , barebox@lists.infradead.org Message-ID: References: <20260210221343.3431882-1-m.felsch@pengutronix.de> <1672b0e8-65ac-4f92-afb7-e5c9eb798537@pengutronix.de> <20260211101451.lyhzyyzxmdydfldj@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260211101451.lyhzyyzxmdydfldj@pengutronix.de> X-Sent-From: Pengutronix Hildesheim X-URL: http://www.pengutronix.de/ X-Accept-Language: de,en X-Accept-Content-Type: text/plain X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260211_045318_881513_8BFBA49B X-CRM114-Status: GOOD ( 39.49 ) X-BeenThere: barebox@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "barebox" X-SA-Exim-Connect-IP: 2607:7c80:54:3::133 X-SA-Exim-Mail-From: barebox-bounces+lore=pengutronix.de@lists.infradead.org X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.whiteo.stw.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-3.9 required=4.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.2 Subject: Re: [RFC PATCH] ARM: dts: i.MX8MP: remove barebox environment handling X-SA-Exim-Version: 4.2.1 (built Wed, 08 May 2019 21:11:16 +0000) X-SA-Exim-Scanned: Yes (on metis.whiteo.stw.pengutronix.de) On Wed, Feb 11, 2026 at 11:14:51AM +0100, Marco Felsch wrote: > Hi Sascha, Ahmad, > > On 26-02-11, Ahmad Fatoum wrote: > > Hi, > > > > On 2/11/26 8:53 AM, Sascha Hauer wrote: > > > On Tue, Feb 10, 2026 at 11:13:40PM +0100, Marco Felsch wrote: > > >> While specifying the barebox environment within the barebox dts is very > > >> helpful for standalone barebox development it's difficult for BSPs which > > >> use this development platform and want to use the GPT mechanism. > > >> As a result BSPs had to manually delete the nodes via a external > > >> provided dts, because we wanted to keep the comfort for the standalone > > >> development flow. > > >> > > >> Lucky commit 86531d4bf7aa ("commands: create createnv command") > > >> introduced a convenient helper to create a barebox environemnt on > > >> demand exactly for this purpose: > > >> > > >> | "We want to move away from describing the barebox environment explicitly > > >> | in the device tree and instead motivate usage of GPT partitions.." > > >> > > >> So start with the i.MX8MP-EVK to encourage the use of GPT partitions and > > >> to make the BSP integration for these development platforms easier. > > > > > > Generally I like this idea, but it breaks the existing users > > > environment and doing this sharp cut might be annoying for the phase > > > where you switch between different barebox versions which could be quite > > > common for development boards. > > Good point, albeit commit 86531d4bf7aa is part of v2025.08.0, so it's > ~6months old. I also don't know how often i.MX8MP-EVK barebox features > are implemented which require to jump between barebox versions. Jumping between versions is something that just happens, be it for bisecting or you have a development and stable branch for a BSP with different barebox versions. > > > > Would be great to have a grace period in which we prefer the UUID > > > environment over the device tree environment (we might do this already) > > > and warn in case we still use the latter. We could stick the warning to > > > a device tree property like "warn-deprecated-env" and remove the > > > environment once they carry this property for a year or so. > > > > > > Just the ideas from the top of my head. Thoughts? > > > > Here's my opinion from a year back: > > https://lore.barebox.org/barebox/1ff0f545-effa-4b87-81b7-524919333777@pengutronix.de/ > > Thanks for the link, I fogot that I've send somthing similar already ^^ > > > I am interested to hear thoughts on it. > > Compared to our suggestion, there will be no eventual removal of the node. > > Both your suggestions are very similar and provide a smother transistion > though. I would like to get rid of the old OF-env handling completely > and therefore prefer Sascha's approach a bit more. Having a fallback is > good, but fallbacks tend to crumble over time since they aren't tested. I like Ahmads approach with a different compatible better as it makes clear that it's only used as a fallback. Whether we remove the device tree nodes from the repository or not doesn't matter now, we can decide that later with both approaches. Sascha -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |