From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Timur Tabi <timur@freescale.com>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>
Subject: Re: Login prompt on a video console instead of serial port?
Date: Tue, 03 May 2011 05:41:04 +0000 [thread overview]
Message-ID: <1304401264.2513.303.camel@pasglop> (raw)
In-Reply-To: <4DBF0DF1.6050207@freescale.com>
On Mon, 2011-05-02 at 15:02 -0500, Timur Tabi wrote:
> McClintock Matthew-B29882 wrote:
> > Don't you have to spawn a terminal on the framebuffer for the login?
>
> I suppose, but I don't know how to do that. And although that would technically
> answer the question in the subject of this thread, I still would have *some*
> boot output on the serial port. It would be nice if I could get all of stdout
> on the video display, and all of stdin from the serial port.
I don't think we have a way to do that unless you can make a serial
"keyboard" device in the input layer. The VT layer will only get its
input from such a thing, maybe that does exist in the depth of legacy
code in there but it has nothing to do with your device-tree.
> > Right now getty spawns the login on the serial port via /etc/inittab.
> > Something similiar is probably needed for the framebuffer.
>
> getty appears to work only with serial devices, since it insists on a baud rate
> as one of the parameters.
No, or no existing distro would work :-)
Just fake a baudrate for the tty's
Cheers,
Ben.
next prev parent reply other threads:[~2011-05-03 5:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 19:30 Login prompt on a video console instead of serial port? Timur Tabi
2011-05-02 19:55 ` McClintock Matthew-B29882
2011-05-02 20:02 ` Timur Tabi
2011-05-03 5:41 ` Benjamin Herrenschmidt [this message]
2011-05-02 20:12 ` Grant Likely
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=1304401264.2513.303.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=B29882@freescale.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=timur@freescale.com \
/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;
as well as URLs for NNTP newsgroup(s).