From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Kim Phillips
<kim.phillips-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
Curt Brune
<curt-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org>
Cc: u-boot-0aAXYlwwYIKGBzrmiIFOJg@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [U-Boot] dtb vs. kernel command line arguments
Date: Mon, 15 Apr 2013 14:37:18 +0100 [thread overview]
Message-ID: <20130415133718.E5DEB3E0AA8@localhost> (raw)
In-Reply-To: <20130304180323.80ef2597c60455f3a358bd79-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
On Mon, 4 Mar 2013 18:03:23 -0600, Kim Phillips <kim.phillips-KZfg59tc24xl57MIdRCFDg@public.gmane.org> wrote:
> On Mon, 4 Mar 2013 10:30:45 -0800
> Curt Brune <curt-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org> wrote:
>
> > Hello -
> >
> > I want to pass a number of arguments from u-boot to the booted kernel.
> > The arguments are needed by user space applications, not the kernel.
> >
> > I can think of two ways:
> >
> > 1. append args by setting "bootargs".
> > 2. add nodes to the dtb before booting.
> >
> > Is there a preferred way to pass information like this?
> >
> > Like I said the arguments are not needed by the kernel device drivers,
> > but by user space applications.
> >
> > I like the structure of nodes in the dtb.
>
> please don't dual-purpose device trees as a mechanism of getting
> arguments through the kernel into userspace - device trees strictly
> describe the hardware.
Why not? The chosen node in particular is for software configuration. I
don't have any problem with passing U-Boot extra data through the chosen
node. Just don't go crazy and please document it.
g.
parent reply other threads:[~2013-04-15 13:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20130304180323.80ef2597c60455f3a358bd79-KZfg59tc24xl57MIdRCFDg@public.gmane.org>]
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=20130415133718.E5DEB3E0AA8@localhost \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=curt-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=kim.phillips-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=u-boot-0aAXYlwwYIKGBzrmiIFOJg@public.gmane.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