From: Andrew Lunn <andrew@lunn.ch>
To: Grant Likely <grant.likely@linaro.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Leif Lindholm <leif.lindholm@linaro.org>,
mark.rutland@arm.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org, ijc@debian.org,
plagnioj@jcrosoft.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] of: support passing console options with stdout-path
Date: Tue, 25 Nov 2014 17:21:21 +0100 [thread overview]
Message-ID: <20141125162121.GC3443@lunn.ch> (raw)
In-Reply-To: <20141125144439.07212C44343@trevor.secretlab.ca>
> > More worrying, barebox does not support the : either. So there is a
> > danger your bootloader suddenly goes silent after a dt blob update.
>
> Is barebox parsing the property? Or updating it? Or both? I've got no
> problem with this patch, but we can also support things like the
> 'current-speed' property in the UART to set a default when the stdout
> path doesn't have any arguments.
Hi Grant
I'm no export with barebox. So i just grep'ed the code.
It parses the property. Also as with linux, of_find_node_by_path()
does not stop at : as you say it should.
There is one case of the property being updated, but that is only for
the PPC mpc85xx.
Barebox does not appear to use 'current-speed' at all.
Andrew
next prev parent reply other threads:[~2014-11-25 16:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 22:23 [PATCH] of: support passing console options with stdout-path Leif Lindholm
2014-11-24 23:00 ` Andrew Lunn
2014-11-25 0:12 ` Leif Lindholm
2014-11-25 6:49 ` Sascha Hauer
2014-11-25 14:44 ` Grant Likely
2014-11-25 16:21 ` Andrew Lunn [this message]
2014-11-25 10:35 ` Mark Rutland
2014-11-25 11:17 ` Leif Lindholm
2014-11-25 12:07 ` Ian Campbell
2014-11-25 14:35 ` Leif Lindholm
2014-11-25 14:55 ` Grant Likely
2014-11-25 12:54 ` Sascha Hauer
2014-11-25 14:58 ` Grant Likely
2014-11-25 15:15 ` Leif Lindholm
2014-11-25 15:20 ` Grant Likely
2014-11-25 15:24 ` Ian Campbell
2014-11-25 15:39 ` Grant Likely
2014-11-25 15:41 ` Ian Campbell
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=20141125162121.GC3443@lunn.ch \
--to=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ijc@debian.org \
--cc=leif.lindholm@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=plagnioj@jcrosoft.com \
--cc=robh+dt@kernel.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