From: Sascha Hauer <sha@pengutronix.de>
To: Matthias Fend <matthias.fend@emfend.at>
Cc: Sam Ravnborg <sam@ravnborg.org>, barebox@lists.infradead.org
Subject: Re: One barebox image for multiple boards
Date: Fri, 13 May 2022 14:23:25 +0200 [thread overview]
Message-ID: <20220513122325.GF25578@pengutronix.de> (raw)
In-Reply-To: <2d23b3c4-8374-6e17-05ab-ed3829d985a0@emfend.at>
On Fri, May 13, 2022 at 02:08:06PM +0200, Matthias Fend wrote:
> Hello Sam,
>
> Am 13.05.2022 um 12:30 schrieb Sam Ravnborg:
> > 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.
> >
> > The skov-imx6 boards was in a similar situation - here the solution was
> > to add enough infrastructure to lowlevel to be able to determine the
> > board variant.
> >
> > Not what you asked for but maybe duplicating the minimal set of
> > infrastructure allows you to determine the board type anyway in lowlevel?
>
> Thank you for pointing out this interesting example.
> Since in this case things like I2C devices are needed for board detection, I
> think putting them in lowlevel init is not a good idea.
It wouldn't be the first board doing I2C in lowlevel init, see
drivers/i2c/busses/i2c-imx-early.c.
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
next prev parent reply other threads:[~2022-05-13 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 8:55 Matthias Fend
2022-05-13 10:30 ` Sam Ravnborg
2022-05-13 12:08 ` Matthias Fend
2022-05-13 12:20 ` Ahmad Fatoum
2022-05-13 18:02 ` Trent Piepho
2022-05-13 12:23 ` Sascha Hauer [this message]
2022-05-13 11:00 ` Sascha Hauer
2022-05-13 12:10 ` Matthias Fend
2022-05-16 8:07 ` Sascha Hauer
2022-05-19 9:25 ` Matthias Fend
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=20220513122325.GF25578@pengutronix.de \
--to=sha@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=matthias.fend@emfend.at \
--cc=sam@ravnborg.org \
/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