From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Fri, 13 May 2022 13:02:47 +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 1npT4J-00BuUT-FV for lore@lore.pengutronix.de; Fri, 13 May 2022 13:02:47 +0200 Received: from bombadil.infradead.org ([2607:7c80:54:e::133]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1npT4H-0002X3-Pw for lore@pengutronix.de; Fri, 13 May 2022 13:02:46 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:From:In-Reply-To:MIME-Version: References:Message-ID:Subject:Cc:To:Date:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Owner; bh=ZeEi8sPPALXgvIIJnN+RIdXm/stwPFRIMkvg95wspnM=; b=4YRhB/rj3nvR9SY0G63JsceKpu M85MyYHGch5ixktcjQputRHBUZTExi9gv1l3jr9S/i8sD7nj+HsARthGKS/UNYRZguWeW/OkwQhZH PdE1tNCZ+Wh23nbJl5myBLThWxtEPUFeHILIYRH77s8ViM0z5mSKjJ1XAr/OH+D4SA8Km+9M/oxl+ f98NJ4D9S9PHic9iuvPM+Xirdf1vFn6uwc2Tqhz2DEJQL+S0AzUZTXylm33m8CQkBhi2PGbaZoHqc p7kMX2ZA6K1lEOE4R+QgMGnSUXlk/5vGMnmQ6vjxBrK0YQXtmxXjxxEu0sPVCGteBbzAYlZkaPchk t80JDO5A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1npT2m-00Fgap-S0; Fri, 13 May 2022 11:01:12 +0000 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1npT2e-00FgTL-3m for barebox@lists.infradead.org; Fri, 13 May 2022 11:01:05 +0000 Received: from ptx.hi.pengutronix.de ([2001:67c:670:100:1d::c0]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1npT2W-00029a-5q; Fri, 13 May 2022 13:00:56 +0200 Received: from sha by ptx.hi.pengutronix.de with local (Exim 4.92) (envelope-from ) id 1npT2V-0002X2-HG; Fri, 13 May 2022 13:00:55 +0200 Date: Fri, 13 May 2022 13:00:55 +0200 To: Matthias Fend Cc: barebox@lists.infradead.org Message-ID: <20220513110055.GE25578@pengutronix.de> References: <1607cab4-d2d3-b5be-99f1-f9f7347d1888@emfend.at> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1607cab4-d2d3-b5be-99f1-f9f7347d1888@emfend.at> X-Sent-From: Pengutronix Hildesheim X-URL: http://www.pengutronix.de/ X-IRC: #ptxdist @freenode X-Accept-Language: de,en X-Accept-Content-Type: text/plain X-Uptime: 12:58:05 up 43 days, 23:27, 89 users, load average: 0.26, 0.30, 0.32 User-Agent: Mutt/1.10.1 (2018-07-13) From: Sascha Hauer X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220513_040104_208953_32CFB595 X-CRM114-Status: GOOD ( 21.15 ) 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" X-SA-Exim-Connect-IP: 2607:7c80:54:e::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.ext.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-5.0 required=4.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.2 Subject: Re: One barebox image for multiple boards X-SA-Exim-Version: 4.2.1 (built Wed, 08 May 2019 21:11:16 +0000) X-SA-Exim-Scanned: Yes (on metis.ext.pengutronix.de) Hi Matthias, On Fri, May 13, 2022 at 10:55:02AM +0200, Matthias Fend wrote: > Hi, > > I'm looking for a solution to support multiple boards with just one barebox > image. The few core components that are relevant for barebox are the same on > all boards, so that the same barebox image runs on all boards. It is > possible to dynamically detect the board type inside barebox, but as this > requires some infrastructure it is not possible during lowlevel init. So > basically Barebox should boot with a minimal core device tree, detect the > board type and then use the corresponding device tree of the detected board. > Something similar to arch/arm/boards/stm32mp15xx-dkx/lowlevel.c but not at > low level. Do you even need the full device tree in barebox? The minimal core device tree might be enough for barebox and only the kernel is then booted with the full device tree. 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 | _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox