From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Raspberry + Usb to TTL Serial Cable issue
Date: Sat, 19 Jul 2014 17:41:11 +0200 [thread overview]
Message-ID: <20140719174111.79e82033@free-electrons.com> (raw)
In-Reply-To: <CAK9TtU1h3RZ=j1cDXD24KjHxTMNzZbZb2w6XuqO0XNr+RXotEw@mail.gmail.com>
Dear Sylvain LG,
On Sat, 19 Jul 2014 17:35:42 +0200, Sylvain LG wrote:
> I changed tty1 to ttyAMA0 and I can log now.
>
> Only kernel messages are displayed, but no daemons messages (for instance,
> "Starting sshd" or the public/private key pair generation).
>
> Why?
Those messages are displayed on the console, so if you have
console=<your serial port> you should see them.
> Can Buildroot be set to configure more than one tty?
There are two separate things:
*/ The kernel console. This one is configured using the console=
kernel parameter, and you can have potentially several ones. This
is where the kernel messages go, as well as the messages of all
userspace processes that do not explicitly define a tty
in /etc/inittab.
*/ The tty on which getty processes are started (getty is the program
that asks for a login). By default, Buildroot only starts one, but
you can create your own /etc/inittab (stored for example in a root
filesystem overlay), and in this case you can start as many getty
programs as you want, on whichever ttys you want.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-19 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-19 12:30 [Buildroot] Raspberry + Usb to TTL Serial Cable issue Sylvain LG
2014-07-19 12:45 ` Vincent
2014-07-19 14:07 ` Thomas Petazzoni
2014-07-19 14:42 ` Sylvain LG
2014-07-19 15:13 ` Thomas Petazzoni
2014-07-19 15:35 ` Sylvain LG
2014-07-19 15:41 ` Thomas Petazzoni [this message]
2014-07-19 15:58 ` Sylvain LG
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=20140719174111.79e82033@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 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.