From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 12/13] ARM: shmobile: alt dts: Add chosen/stdout-path
Date: Tue, 03 Feb 2015 01:13:12 +0300 [thread overview]
Message-ID: <54CFF678.6070009@cogentembedded.com> (raw)
In-Reply-To: <CAMuHMdUoc0f0WReqx86Qe35zwnbT3j49q5b+fFHupQa+3QsKag@mail.gmail.com>
Hello.
On 01/31/2015 01:18 PM, Geert Uytterhoeven wrote:
>>> Add a stdout-path property so that automatic console selection works
>>> in the absence of a "console=" parameter on the kernel command line.
>>> Note that we have to keep the "console=ttySC0,38400" parameter in
>>> chosen/bootargs, else the console will use the default setting of 115200
>>> baud.
>> I've looked at the code and it appears that one can still specify a baud
>> rate after ':' even in the "stdout-path" prop.
> That's correct. I believe that support was added later.
> Can you please send a patch?
Looks like Simon wants all boards to work at 115200 which is the default.
> Spaciba!
Heh, actually it's "sbasibo". :-)
> Gr{oetje,eeting}s,
> Geert
WBR, Sergei
next prev parent reply other threads:[~2015-02-02 22:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 15:11 [PATCH v2 00/13] ARM: shmobile: dts: Add chosen/stdout-path Geert Uytterhoeven
[not found] ` <1412349104-18724-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2014-10-03 15:11 ` [PATCH v2 01/13] ARM: shmobile: emev2 dtsi: Use generic names for device nodes Geert Uytterhoeven
2014-10-03 15:11 ` [PATCH v2 02/13] ARM: shmobile: emev2 dtsi: Add uart* labels for easier referencing Geert Uytterhoeven
2014-10-03 15:11 ` [PATCH v2 03/13] ARM: shmobile: kzm9d dts: Add chosen/stdout-path Geert Uytterhoeven
2014-10-06 2:36 ` Simon Horman
2014-10-06 8:43 ` Geert Uytterhoeven
2014-10-06 9:05 ` Simon Horman
2014-10-03 15:11 ` [PATCH v2 04/13] ARM: shmobile: genmai " Geert Uytterhoeven
2014-10-03 15:11 ` [PATCH v2 05/13] ARM: shmobile: ape6evm-reference " Geert Uytterhoeven
2014-10-03 15:11 ` [PATCH v2 06/13] ARM: shmobile: armadillo800eva " Geert Uytterhoeven
2014-10-03 15:11 ` [PATCH v2 07/13] ARM: shmobile: bockw-reference " Geert Uytterhoeven
2014-10-03 15:11 ` [PATCH v2 08/13] ARM: shmobile: marzen " Geert Uytterhoeven
2014-10-03 15:11 ` [PATCH v2 09/13] ARM: shmobile: lager " Geert Uytterhoeven
2014-10-03 15:11 ` [PATCH v2 10/13] ARM: shmobile: henninger " Geert Uytterhoeven
2014-10-03 15:11 ` [PATCH v2 11/13] ARM: shmobile: koelsch " Geert Uytterhoeven
2014-10-03 15:11 ` [PATCH v2 12/13] ARM: shmobile: alt " Geert Uytterhoeven
2015-01-30 22:33 ` Sergei Shtylyov
[not found] ` <54CC06A4.9040408-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2015-01-31 10:18 ` Geert Uytterhoeven
2015-02-02 22:13 ` Sergei Shtylyov [this message]
2015-02-03 0:42 ` Simon Horman
2014-10-03 15:11 ` [PATCH v2 13/13] ARM: shmobile: kzm9g-reference " Geert Uytterhoeven
2014-10-06 2:40 ` [PATCH v2 00/13] ARM: shmobile: " Simon Horman
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=54CFF678.6070009@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).