From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Graf Alex <alex.graf@siemens.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: AW: Serial Console at MPC8xx SCC1?
Date: Thu, 14 Aug 2003 12:19:41 +0200 [thread overview]
Message-ID: <3F3B623D.1090708@imc-berlin.de> (raw)
In-Reply-To: <791B3205DB661A42B4BFE5464A7D1D02010E461A@chzugexch01.abatos.com>
Alex,
> Yes this works very well!
> Be sure you have defined CONFIG_SERIAL_CONSOLE_PORT for your uart.c! If you
> use SMC1+2 for uarts, define it as 2!
Yeah. I found that one!
I was under the (stupid) impression that it would be enough to just
pass console=ttyS2,115200 to the linux kernel.
I think it wouldn't be too hard to make it work like that. (I think
there'S just too much hardcoded...) Maybe I give it a try after my
vacations...
Thanks anyway!
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-08-14 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 9:30 AW: Serial Console at MPC8xx SCC1? Graf Alex
2003-08-14 10:19 ` Steven Scholz [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=3F3B623D.1090708@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=alex.graf@siemens.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).