From: Mark Hatle <fray@mvista•com>
To: Aman <aman@mistralsoftware•com>
Cc: linuxppc embedded <linuxppc-embedded@lists•linuxppc.org>
Subject: Re: Serial Console
Date: Tue, 04 Mar 2003 09:40:13 -0600 [thread overview]
Message-ID: <3E64C8DD.5010100@mvista.com> (raw)
In-Reply-To: <000801c2e25d$d560ec10$370da8c0@aman>
Aman wrote:
> Hi
>
> In the Redhat 7.0 linux, I was able to enable/disable the serial console
> using the following command in the inittab
> " T0:12345:respawn:/sbin/getty ttyS0 9600 vt100"
That is actually not a serial "console", it is a serial "login". (It's a small
distinction but an important one)
On a workstation system (with say VGA), when the system boots the "console"
comes up and displays your boot messages. Eventually init executes and starts a
login sesssion on the same device as the default console. Thus your screen has
both a "console" and "login" active.
> However in the case of the 440 Linux the serial console is enabled already.
> I wanted to know how this enabling is done. Can someone add some points to
> this.
Probably with your configuration, the default system console is on a serial
port. This means all boot and kernel messages will go there.
Again you will want to start a login process via init in order to do multi-user
logins.
(But in the embedded world, init, getty/login and such aren't required. You can
just as easily boot right into /bin/sh.)
Now back to your original question.. How is it enabled:
The console is enabled either by the system configuration or by the kernel
command line, "console=". Look in the "Documentation" directory in the kernel,
something in there explains serial consoles and the cmdline semantics.
--Mark
>
> Thanking you in advance
> Regards
> Aman
>
>
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-04 15:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 14:53 Serial Console Aman
2003-03-04 15:40 ` Mark Hatle [this message]
2003-03-04 17:06 ` Ibon Gotxi Garcia
2003-03-04 19:09 ` Dave Wolfe
-- strict thread matches above, loose matches on Subject: below --
2005-10-05 2:36 serial console KokHow Teh
2005-10-05 12:23 ` Vitaly Bordug
2005-10-05 2:32 KokHow Teh
2005-10-04 6:54 KokHow Teh
2005-10-04 15:11 ` David Jander
2005-10-04 15:16 ` Vitaly Bordug
2005-10-05 9:16 ` David Jander
2005-07-30 1:06 Serial console Daniel Ann
2005-07-30 1:19 ` Josh Boyer
2005-07-30 1:36 ` Daniel Ann
2005-07-30 5:46 ` Daniel Ann
2005-07-30 1:27 ` Ricardo Scop
2005-07-30 1:34 ` Daniel Ann
2005-07-30 10:37 ` Anton Wöllert
2005-08-01 1:27 ` Daniel Ann
2005-08-02 3:38 ` JohnsonCheng
2005-08-02 13:39 ` Kumar Gala
2005-08-03 0:16 ` Daniel Ann
2003-01-16 21:06 Serial Console Aman
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=3E64C8DD.5010100@mvista.com \
--to=fray@mvista$(echo .)com \
--cc=aman@mistralsoftware$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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