mail archive of the barebox mailing list
 help / color / mirror / Atom feed
* One barebox image for multiple boards
@ 2022-05-13  8:55 Matthias Fend
  2022-05-13 10:30 ` Sam Ravnborg
  2022-05-13 11:00 ` Sascha Hauer
  0 siblings, 2 replies; 10+ messages in thread
From: Matthias Fend @ 2022-05-13  8:55 UTC (permalink / raw)
  To: barebox


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.
Maybe I missed something, but I couldn't find such a scenario in the 
existing board code yet.

Is there a suggestion on how to best implement such a system, or is 
there perhaps a board that uses something like this?


barebox mailing list

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2022-05-19  9:27 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-13  8:55 One barebox image for multiple boards 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
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox