On Thu, Jan 17, 2019 at 02:28:45PM +0100, Sascha Hauer wrote: > On Thu, Jan 17, 2019 at 03:44:22PM +0300, Серафим Долбилов wrote: > > Reading Barebox's source code I found that `examle.dts` (e.g.) becomes > > `example.dtb`, then `example.dtb.o`, and is finally linked into PBL, > > being "catched" in lwl-code by `extern char __dtb_example_start[];` > > symbol. Then this symbol is used in `barebox_arm_entry()` function, > > etc... So I just want to know, why do we link DT into PBL, and what is > > PBL exactly, if not an self-unpacking-and-relocating image? > > PBL is for PreBootLoader. Yes, it's a self extracting image. During > building of barebox a single barebox binary and one to many PBL images > are built. Each PBL image is for one specific board. It's the PBL which > actually knows the board type and it'll pass the device tree to the > barebox binary to let it know which hardware it is running on. This is > all done to build barebox for multiple boards in a single go. There are also these two section in the docs, if it helps: https://www.barebox.org/doc/latest/user/pbl.html https://www.barebox.org/doc/latest/user/multi-image.html - Roland -- Roland Hieber | r.hieber@xxxxxxxxxxxxxx | Pengutronix e.K. | https://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
