All of 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:24:44 +0000	[thread overview]
Message-ID: <1418829884.4132.13.camel@synopsys.com> (raw)
In-Reply-To: <20141217161406.1f418842@free-electrons.com>

Hi Thomas,

On Wed, 2014-12-17 at 16:14 +0100, Thomas Petazzoni wrote:
> Dear Alexey Brodkin,
> 
> On Wed, 17 Dec 2014 15:03:12 +0000, Alexey Brodkin wrote:
> 
> > 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.
> 
> Ah, yes I haven't looked at the baudrate issue. Isn't there a way to
> not pass any baudrate to getty, and let it use whatever baudrate is
> already configured on the device?

Probably not. At least in case of Busybox I saw this on attempt to
execute getty without baudrate at all.

--->---
BAUD_RATE of 0 leaves it unchanged

BusyBox v1.22.1 (2014-12-15 15:41:48 MSK) multi-call binary.

Usage: getty [OPTIONS] BAUD_RATE[,BAUD_RATE]... TTY [TERMTYPE]
Open TTY, prompt for login name, then invoke /bin/login

        -h              Enable hardware RTS/CTS flow control
        -L              Set CLOCAL (ignore Carrier Detect state)
        -m              Get baud rate from modem's CONNECT status
message
        -n              Don't prompt for login name
        -w              Wait for CR or LF before sending /etc/issue
        -i              Don't display /etc/issue
        -f ISSUE_FILE   Display ISSUE_FILE instead of /etc/issue
        -l LOGIN        Invoke LOGIN instead of /bin/login
        -t SEC          Terminate after SEC if no login name is read
        -I INITSTR      Send INITSTR before anything else
        -H HOST    
--->---

-Alexey

  reply	other threads:[~2014-12-17 15:24 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 [this message]
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=1418829884.4132.13.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.