Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] systemd: let getty instead of serial-getty handle /dev/console
Date: Sun, 25 Sep 2016 23:44:14 +0200	[thread overview]
Message-ID: <20160925234414.232f7008@gmx.net> (raw)
In-Reply-To: <46b6edf4-6e2e-7200-133c-0321299f5805@je-eigen-domein.nl>

Hello Floris,

On Thu, 22 Sep 2016 21:25:59 +0200, Floris Bos <bos@je-eigen-domein.nl> wrote:

> On 09/22/2016 08:50 PM, Peter Seiderer wrote:
> > Hello Floris,
> >
> > On Wed, 21 Sep 2016 23:47:02 +0200, Floris Bos <bos@je-eigen-domein.nl> wrote:
> >
> >> On 09/21/2016 10:05 PM, Peter Seiderer wrote:
> >>> Hello *,
> >>>
> >>> On Wed, 21 Sep 2016 09:01:37 +0200, Peter Korsgaard <peter@korsgaard.com> wrote:
> >>>
> >>>>>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> >>>>    > Floris, All,
> >>>>    > On 2016-09-09 18:10 +0200, Floris Bos spake thusly:
> >>>>    >> The serial-getty unit depends on dev-%i.device which does not
> >>>>    >> seem to be created for /dev/console
> >>>>    >> Workaround this by letting normal getty unit handle things
> >>>>    >> if BR2_TARGET_GENERIC_GETTY_PORT is set to 'console'
> >>>>    >>
> >>>>    >> Signed-off-by: Floris Bos <bos@je-eigen-domein.nl>
> >>>>
> >>>>    > I haven't tested that, but I think this is OK just on principle.
> >>>>
> >>>>    > I just wonder if that behaves correctly when console is a serial line or
> >>>>    > anything else (e.g. a VT on HDMI, or through a debug channel...)
> >>>>
> >>>> Yeah, me too. Does anybody know what the difference exactly is between
> >>>> getty/serial-getty, and when one should be used over the other?
> >>>>
> >>> Tested for the rpi3/glibc/systemd case and failed: I get a doubled
> >>> (and unusable) ' Welcome to Buildroot/buildroot login:' on serial and
> >>> no login on hdmi...
> >> Empty cmdline.txt will give hdmi.
> >>
> >> Recall you need "console=serial0,115200 console=tty1" with tty1 last in
> >> cmdline.txt if you want them simultaneous.
> > Changed cmdline.txt to:
> >
> > 	root=/dev/mmcblk0p2 rootwait console=ttyAMA0,115200 console=tty1
> >
> > Which gives me two (functional) logins on serial and hdmi.
> >
> > But I think changing package/rpi-firmware/cmdline.txt unconditional will
> > break the other Init systems, see commit log from last patch touching
> > cmdline.txt ([1):
> >
> >    ...change BR2_TARGET_GENERIC_GETTY_PORT to "console", so it starts a
> >    getty on the last console= passed to the kernel, ttyAMA0...
> 
> Will withdraw my patch then, and wait for someone else to come up with a 
> better solution.
> 

Ups, sorry, did not want to discourage you...

> I think the one-size-fits all cmdline.txt that listens to both on HDMI 
> and serial console by default makes things too complicated anyway.
> 

Maybe its feasible to list all wanted login ports in BR2_TARGET_GENERIC_GETTY_PORT
and only add the specified named systemd service links (an no generator ones)?

Regards,
Peter

>
> Yours sincerely,
> 
> Floris Bos
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

      reply	other threads:[~2016-09-25 21:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 16:10 [Buildroot] [PATCH] systemd: let getty instead of serial-getty handle /dev/console Floris Bos
2016-09-11 20:00 ` Thomas Petazzoni
2016-09-11 21:09 ` Yann E. MORIN
2016-09-21  7:01   ` Peter Korsgaard
2016-09-21 20:05     ` Peter Seiderer
2016-09-21 21:47       ` Floris Bos
2016-09-22 18:50         ` Peter Seiderer
2016-09-22 19:25           ` Floris Bos
2016-09-25 21:44             ` Peter Seiderer [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=20160925234414.232f7008@gmx.net \
    --to=ps.report@gmx.net \
    --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