From: Wolfram Sang <wsa@the-dreams.de>
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 11:35:31 +0100 [thread overview]
Message-ID: <20150311103530.GA5491@katana> (raw)
In-Reply-To: <CAMuHMdVSbYYGQyOjce87Q_dMHvh9du1EkgOgC+CBgrMys++mkA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
> Hence all pieces of the puzzle are available to userspace...
> Is there another way?
My hackish way is to parse dmesg, adapt inittab at runtime and make init reload
it. Not exactly production quality, though:
+ l=$(dmesg | sed -n '/console.*enabled/ s/.*\[\(tty[A-Z]\+[0-9]\+\)\].*/\1/; T; p; q')
+ sed -i s/ttyS0/$l/g /etc/inittab
+ kill -s SIGHUP 1
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-11 10:35 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 [this message]
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
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=20150311103530.GA5491@katana \
--to=wsa@the-dreams.de \
--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).