From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: wanting to clarify terminology regarding kernel and device trees
Date: Mon, 7 Jul 2014 08:48:00 +0200 [thread overview]
Message-ID: <20140707064800.GH23235@pengutronix.de> (raw)
In-Reply-To: <alpine.LFD.2.11.1407040846490.22603@localhost>
On Fri, Jul 04, 2014 at 09:01:04AM -0400, Robert P. J. Day wrote:
>
> reading the user manual, section "Booting Linux", about to do a bit
> of cleanup there, and i read this:
>
> "NOTE: it may happen that barebox is probed from the devicetree, but
> you have want to start a Kernel without passing a devicetree. In this
> case call oftree -f to free the internal devicetree before calling
> bootm"
>
> i'm puzzled by the phrase "it may happen that barebox is probed from
> the devicetree". i'm sure this is not meant to imply that the device
> tree itself does any actual "probing" of barebox. i'm guessing that
> what this should really say is something like, "even if barebox has
> been built with an internal device tree, you may want to start the
> kernel without passing that device tree." thus, "oftree -f", etc,
> etc.
That is what I wanted to say, yes.
This sometimes happens on ARM when you have a new barebox with internal
devicetree but want to start an older kernel which needs the ATAG list
to start.
>
> also, at the risk of being overly pedantic, i would distinguish
> between the actions of "probing" and "consulting." i would normally
> use the word "probe" in the sense of probing for possible devices, not
> knowing if they're there or not.
Indeed we do not have this kind of probing here, so the term might be
misleading.
> i would use the word "consult" when
> one is reading or processing something that is known to be there, such
> as the device tree.
How about devices that are instantiated or populated from the
devicetree? I never heard the word "consult" in this context.
>
> some probably silly questions about device trees coming up shortly
Hm, most of the time such silly question turn out to be not silly at all
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
prev parent reply other threads:[~2014-07-07 6:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 13:01 Robert P. J. Day
2014-07-07 6:48 ` Sascha Hauer [this message]
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=20140707064800.GH23235@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rpjday@crashcourse.ca \
/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