From: Peter Hurley <peter@hurleysoftware.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Grant Likely <grant.likely@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Cao Minh Hiep <cm-hiep@jinso.co.jp>,
Nobuhiro Iwamatsu <iwamatsu@nigauri.org>,
Linux-SH <linux-sh@vger.kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>,
Sakato Ryusuke <ryusuke.sakato.bx@renesas.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: chosen/stdout-path and userland (Re: Can't boot kernel v4.0-rc2 on Koelsch)
Date: Wed, 11 Mar 2015 09:42:41 -0400 [thread overview]
Message-ID: <55004651.2000205@hurleysoftware.com> (raw)
In-Reply-To: <CAMuHMdWjHnX4NS2Z7MMg9FBjDpo41h517U3t+ndSCzhGKDLCvA@mail.gmail.com>
Hi Geert,
On 03/11/2015 09:23 AM, Geert Uytterhoeven wrote:
> Hi Peter,
>
> On Wed, Mar 11, 2015 at 2:05 PM, Peter Hurley <peter@hurleysoftware.com> wrote:
>> The first console listed is the primary console.
>> tty0 is not resolved to its underlying tty device name.
>
> Are you sure about that? Isn't the last one the primary console?
>
> root@koelsch:~# cat /sys/class/tty/console/active
> tty0 ttySC0
>
> If tty0 would be the primary console, getty on /dev/console wouldn't work for
> my serial console, as only input on the primary console can be read through
> /dev/console if my memory serves me well (or perhaps this has changed?).
>
> Ah, Documentation/ABI/testing/sysfs-tty agrees with me:
>
> What: /sys/class/tty/console/active
> Date: Nov 2010
> Contact: Kay Sievers <kay.sievers@vrfy.org>
> Description:
> Shows the list of currently configured
> console devices, like 'tty1 ttyS0'.
> The last entry in the file is the active
> device connected to /dev/console.
Did I write 'first'? <blushes>
Yeah, it is 'last', as the documentation states.
>> That said, is the original reporter of this problem even interested in
>> upgrading their userspace, even if this is fixed in Linaro eventually?
>> What about other Linaro users?
>
> We'll see...
>
>> I think the only reasonable course here is to continue to support
>> "console=" in /chosen/bootargs.
>
> Hmm...
> If you really need it, you can always add it to the U-Boot bootargs variable.
Is u-boot a given?
Regards,
Peter Hurley
prev parent reply other threads:[~2015-03-11 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 10:08 chosen/stdout-path and userland (Re: Can't boot kernel v4.0-rc2 on Koelsch) Geert Uytterhoeven
2015-03-11 10:35 ` Wolfram Sang
2015-03-11 13:05 ` Peter Hurley
[not found] ` <55003D82.1080601-WaGBZJeGNqdsbIuE7sb01tBPR1lH4CV8@public.gmane.org>
2015-03-11 13:23 ` Geert Uytterhoeven
2015-03-11 13:42 ` Peter Hurley [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=55004651.2000205@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=cm-hiep@jinso.co.jp \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=grant.likely@linaro.org \
--cc=horms@verge.net.au \
--cc=iwamatsu@nigauri.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=ryusuke.sakato.bx@renesas.com \
--cc=yoshihiro.shimoda.uh@renesas.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).