From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] system: add "askfirst shell" as an option for busybox init
Date: Wed, 17 Dec 2014 17:28:18 +0100 [thread overview]
Message-ID: <20141217172818.250714b4@free-electrons.com> (raw)
In-Reply-To: <1418833123.4132.22.camel@synopsys.com>
Dear Alexey Brodkin,
On Wed, 17 Dec 2014 16:18:44 +0000, Alexey Brodkin wrote:
> > > Then the question is why this is not a default in Buildroot?
> > > IMHO most of the time kernel's bootcmd has console set so explicit setup
> > > of tty in Buildroot might be required in some corner cases only.
> >
> > I agree, maybe we should make this the default. What happens on
> > PC-style platforms? Is console= typically set to tty1 ?
>
> Well from dmesg output of my Fedora 21 I see this:
> --->---
> [ 0.000000] console [tty0] enabled
> --->---
> Is this what you're looking for?
I don't know if running a getty on tty0 actually works. tty0 is
actually a "fake" device that points to the current virtual console. To
be tested, maybe with the Qemu/x86 emulation.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-17 16:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 8:56 [Buildroot] [PATCH] system: add "askfirst shell" as an option for busybox init Alexey Brodkin
2014-12-15 11:43 ` Károly Kasza
2014-12-15 12:31 ` Alexey Brodkin
2014-12-16 7:14 ` Thomas Petazzoni
2014-12-17 15:03 ` Alexey Brodkin
2014-12-17 15:14 ` Thomas Petazzoni
2014-12-17 15:24 ` Alexey Brodkin
2014-12-17 15:36 ` Thomas Petazzoni
2014-12-17 15:50 ` Alexey Brodkin
2014-12-17 15:53 ` Jeremy Rosen
2014-12-17 16:07 ` Thomas Petazzoni
2014-12-17 16:08 ` Thomas Petazzoni
2014-12-17 16:18 ` Alexey Brodkin
2014-12-17 16:28 ` Thomas Petazzoni [this message]
2014-12-23 9:40 ` Alexey Brodkin
2014-12-23 10:19 ` Thomas Petazzoni
2014-12-21 21:09 ` Thomas Petazzoni
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=20141217172818.250714b4@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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