Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] system: add "askfirst shell" as an option for busybox init
Date: Tue, 23 Dec 2014 09:40:27 +0000	[thread overview]
Message-ID: <1419327626.2781.2.camel@synopsys.com> (raw)
In-Reply-To: <20141217172818.250714b4@free-electrons.com>

Hi Thomas,

On Wed, 2014-12-17 at 17:28 +0100, Thomas Petazzoni wrote:
> 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.

I've just tried Qemu/x86 and with following config it worked like a
charm:
--->---
BR2_x86_pentiumpro=y
BR2_KERNEL_HEADERS_VERSION=y
BR2_DEFAULT_KERNEL_VERSION="3.17.2"
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_17=y
BR2_TARGET_GENERIC_GETTY_PORT="console"
BR2_TARGET_GENERIC_GETTY_BAUDRATE_KEEP=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.17.2"
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/qemu/x86/linux-3.17.config"
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
--->---

So then I think it's time for a patch that by default selects:
1. BR2_TARGET_GENERIC_GETTY_PORT="console"
2. BR2_TARGET_GENERIC_GETTY_BAUDRATE_KEEP=y

Any objections?

-Alexey

  reply	other threads:[~2014-12-23  9:40 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
2014-12-23  9:40                   ` Alexey Brodkin [this message]
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=1419327626.2781.2.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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