From: Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: Devicetree Discuss
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: Specifying the console device using an alias
Date: Mon, 18 Aug 2014 21:19:09 +0200 [thread overview]
Message-ID: <20140818191909.GA5352@pengutronix.de> (raw)
In-Reply-To: <CAPnjgZ1S-HVZJ7kzt=YKT+jjZEtLdmZSnr6kmNVf+paGKdrgoQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Simon,
On Thu, Aug 14, 2014 at 10:02:10PM -0600, Simon Glass wrote:
> (correct list)
>
> On 14 August 2014 21:42, Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org> wrote:
> > Hi,
> >
> > In U-Boot we currently specify the console device (typically serial)
> > using something like:
> >
> > aliases {
> > console = "/serial@1234";
> > }
> >
> > But the question has come up as to whether this should be done another
> > way. I see the "linux.stdout" property in the /chosen node.
> >
> > I am concerned that making use of the /chosen node in U-Boot might
> > confuse a lot of people, since this node is normally used to provide
> > selections for the OS to use when booting. If we did use /chosen, then
> > linux,stdout seems plain wrong but perhaps u-boot,stdout could be used
> > instead.
See ePAPR. There's a stdout-path property specified, without linux,
prefix.
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 |
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-08-18 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPnjgZ2A=DkGSnFLy1En8bH0pZAUAEWCWz_jQ941g3QQEUN9NQ@mail.gmail.com>
[not found] ` <CAPnjgZ2A=DkGSnFLy1En8bH0pZAUAEWCWz_jQ941g3QQEUN9NQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-15 4:02 ` Specifying the console device using an alias Simon Glass
[not found] ` <CAPnjgZ1S-HVZJ7kzt=YKT+jjZEtLdmZSnr6kmNVf+paGKdrgoQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-15 17:22 ` Simon Glass
[not found] ` <CAPnjgZ3Yuov+2tHHbjepspfom2ibJQmdEL3TfEq8nAQofqfsEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-15 17:35 ` Simon Glass
2014-08-18 19:19 ` Sascha Hauer [this message]
[not found] ` <20140818191909.GA5352-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-08-20 17:25 ` Simon Glass
[not found] ` <CAPnjgZ3YU8zy48UrxByZjY5rkK3mK7Quvi6O3kWtBfW6ttG6VA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-20 17:39 ` Fabio Estevam
[not found] ` <CAOMZO5BcMjSV+cgLq1+AF8+n+rzTtSm51yu7Guw+z+Bs6s=EGA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-01 20:08 ` Simon Glass
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=20140818191909.GA5352@pengutronix.de \
--to=s.hauer-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=sjg-F7+t8E8rja9g9hUCZPvPmw@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;
as well as URLs for NNTP newsgroup(s).