From: Shawn Guo <shawnguo@kernel.org>
To: Stefan Agner <stefan@agner.ch>
Cc: devicetree@vger.kernel.org, shawn.guo@linaro.org,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: vf-colibri: define stdout-path property
Date: Fri, 17 Jul 2015 10:55:53 +0800 [thread overview]
Message-ID: <20150717025553.GA12927@tiger> (raw)
In-Reply-To: <bed79bcac594f3efece6acb3c24ae543@agner.ch>
On Wed, Jul 15, 2015 at 04:05:50PM +0200, Stefan Agner wrote:
> On 2015-07-13 17:10, Shawn Guo wrote:
> > On Fri, Jul 03, 2015 at 10:06:39AM +0200, Stefan Agner wrote:
> >> Define Vybrid's UART0, connected to the Colibri pinout UART_A, as
> >> standard output.
> >>
> >> Signed-off-by: Stefan Agner <stefan@agner.ch>
> >> ---
> >> arch/arm/boot/dts/vf-colibri-eval-v3.dtsi | 1 +
> >> 1 file changed, 1 insertion(+)
> >>
> >> diff --git a/arch/arm/boot/dts/vf-colibri-eval-v3.dtsi b/arch/arm/boot/dts/vf-colibri-eval-v3.dtsi
> >> index 2cbe663..cb199ae 100644
> >> --- a/arch/arm/boot/dts/vf-colibri-eval-v3.dtsi
> >> +++ b/arch/arm/boot/dts/vf-colibri-eval-v3.dtsi
> >> @@ -10,6 +10,7 @@
> >> / {
> >> chosen {
> >> bootargs = "console=ttyLP0,115200";
> >> + stdout-path = "serial0:115200n8";
> >
> > With this change, can bootargs just be dropped?
>
> I guess it would break a (fairly old) kernel which does not support
> stdout-path yet?
The DT ABI requires that the new kernel doesn't break anything
with old DTB, but doesn't require the compatibility between new DTB
and old kernel.
Shawn
prev parent reply other threads:[~2015-07-17 2:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 8:06 [PATCH] ARM: dts: vf-colibri: define stdout-path property Stefan Agner
2015-07-13 15:10 ` Shawn Guo
2015-07-15 14:05 ` Stefan Agner
2015-07-17 2:55 ` Shawn Guo [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=20150717025553.GA12927@tiger \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=stefan@agner.ch \
/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).