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: Wed, 17 Dec 2014 15:03:12 +0000	[thread overview]
Message-ID: <1418828592.4132.7.camel@synopsys.com> (raw)
In-Reply-To: <20141216081450.6438bdb6@free-electrons.com>

Hi Thomas,

On Tue, 2014-12-16 at 08:14 +0100, Thomas Petazzoni wrote:
> Dear Alexey Brodkin,
> 
> On Mon, 15 Dec 2014 11:56:24 +0300, Alexey Brodkin wrote:
> > Consider following cases:
> >  * Buildroot only builds rootfs that could be used on systems with
> >    different default serial ports (ttyS0, ttyS1, ttyAMA3 etc)
> 
> To achieve this, there is no need for a new option, just specify
> "console" as the terminal on which to run getty. The only change needed
> is to add "console" to /etc/securetty.

Well, actually putting "console" in BR2_TARGET_GENERIC_GETTY_PORT
resolves only part of issues - need to specify particular tty.

But still we have serial port settings like baudrate.
BR2_TARGET_GENERIC_GETTY_BAUDRATE_x must match your serial port
settings.

So we're loosing flexibility of my approach here, but what is even more
important imagine if there're 2 serial ports in the system and they have
different baudrates but both properly described in kernel bootargs. With
BR2_TARGET_GENERIC_GETTY only 1 console could be used then but not
either of them.

-Alexey

  reply	other threads:[~2014-12-17 15:03 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 [this message]
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
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=1418828592.4132.7.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