From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: wanting to clarify terminology regarding kernel and device trees
Date: Fri, 4 Jul 2014 09:01:04 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407040846490.22603@localhost> (raw)
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.
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. i would use the word "consult" when
one is reading or processing something that is known to be there, such
as the device tree.
some probably silly questions about device trees coming up shortly
...
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2014-07-04 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 13:01 Robert P. J. Day [this message]
2014-07-07 6:48 ` 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=alpine.LFD.2.11.1407040846490.22603@localhost \
--to=rpjday@crashcourse.ca \
--cc=barebox@lists.infradead.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