From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Серафим Долбилов" <s.dlblv@ya.ru>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [HELP] Barebox porting
Date: Thu, 17 Jan 2019 14:28:45 +0100 [thread overview]
Message-ID: <20190117132845.wkyeunk3b5nze7jv@pengutronix.de> (raw)
In-Reply-To: <3289771547729062@iva1-5148b5385b62.qloud-c.yandex.net>
On Thu, Jan 17, 2019 at 03:44:22PM +0300, Серафим Долбилов wrote:
> 17.01.2019, 10:59, "Sascha Hauer" <s.hauer@pengutronix.de>:
> > You can have any devicetree by adding it to arch/arm/dts/Makefile:
> >
> > pbl-dtb-$(CONFIG_MACH_FREESCALE_MX51_PDK) += imx51-babbage.dtb.o
> >
> > Then add a declaration for it (replace beginning of filename with
> > __dtb_, .dtb.o with _start and '-' with '_'):
> >
> > extern char __dtb_imx51_babbage_start[];
> >
> > And then you can use it. Use obj-dtb-$(CONFIG_MACH_FREESCALE_MX51_PDK)
> > when you want to have it in the full barebox image rather than in the
> > PBL.
>
> In which cases do I need to link it to the full image?
>
> Frankly speaking, I just want DT to be parsed by the bootloader (in
> order to detect such devices as USB, ethernet PHY, etc, and run their
> drivers) and then passed to Linux kernel (when boot command is
> invoked).
> So all my questions about DT are coming from around this problem.
This is what barebox does by default.
>
> 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.
Regards
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 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:[~2019-01-17 13:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44943261547037040@iva5-750e13568e4d.qloud-c.yandex.net>
2019-01-09 12:40 ` Серафим Долбилов
2019-01-09 13:03 ` Sascha Hauer
2019-01-16 15:14 ` Серафим Долбилов
2019-01-16 15:37 ` Серафим Долбилов
2019-01-16 17:29 ` Sam Ravnborg
2019-01-16 17:28 ` Sam Ravnborg
2019-01-16 18:48 ` Antony Pavlov
2019-01-16 15:59 ` Серафим Долбилов
2019-01-17 7:59 ` Sascha Hauer
2019-01-17 12:44 ` Серафим Долбилов
2019-01-17 13:28 ` Sascha Hauer [this message]
2019-01-17 13:43 ` Roland Hieber
2019-01-17 14:48 ` Серафим Долбилов
2019-01-17 16:26 ` Sam Ravnborg
2019-01-17 21:06 ` Sascha Hauer
2019-01-18 15:01 ` Seraphim Dolbilov
2019-01-18 15:14 ` Sascha Hauer
2019-01-18 16:30 ` Seraphim Dolbilov
2019-01-21 12:34 Seraphim Dolbilov
2019-01-21 14:28 ` Seraphim Dolbilov
2019-01-21 15:12 ` Sascha Hauer
2019-01-21 15:35 ` Seraphim Dolbilov
2019-01-21 16:35 ` Sam Ravnborg
2019-01-21 16:43 ` Seraphim Dolbilov
2019-01-22 6:33 ` Sascha Hauer
2019-01-22 14:07 ` Seraphim Dolbilov
2019-01-22 14:42 ` Sascha Hauer
2019-01-22 16:12 ` Seraphim Dolbilov
2019-01-23 9:11 ` Sascha Hauer
2019-01-23 10:01 ` Seraphim Dolbilov
2019-01-23 10:17 ` Sascha Hauer
2019-01-25 12:18 ` Seraphim Dolbilov
2019-01-25 14:11 ` Seraphim Dolbilov
2019-01-28 8:46 ` Sascha Hauer
2019-01-28 8:44 ` Sascha Hauer
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=20190117132845.wkyeunk3b5nze7jv@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.dlblv@ya.ru \
/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