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: Sun, 21 Dec 2014 22:09:13 +0100 [thread overview]
Message-ID: <20141221220913.5cb62321@free-electrons.com> (raw)
In-Reply-To: <1418633784-7709-1-git-send-email-abrodkin@synopsys.com>
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)
> * Target system has multiple serial ports and in kernel command
> line users/developers may select different serial ports as
> debug consoles
>
> In both cases hard-coded with BR2_TARGET_GENERIC_GETTY tty will
> only work for 1 particular serial port.
>
> This change introduces an option to use whatever existing console.
> For example console selected in kernel's command line will be used.
>
> I'm not sure if the same thing works for SysVinit so marking it
> dependent on Busybox init.
>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: Anton Kolesov <akolesov@synopsys.com>
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
In the light of the discussion that has taken place, we have found a
solution that apparently matches your use case, by using the existing
Buildroot options. Therefore, I've marked your patch as Rejected in
patchwork. If you disagree, do not hesitate to re-send an updated
version with an extended justification.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-12-21 21:09 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
2014-12-23 10:19 ` Thomas Petazzoni
2014-12-21 21:09 ` Thomas Petazzoni [this message]
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=20141221220913.5cb62321@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