From: Vitaly Bordug <vitaly_@f-m.fm>
To: ning <ningmin@yahoo.co.jp>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Serial console problem on MPC8272ADS board
Date: Tue, 01 Feb 2005 20:10:46 +0300 [thread overview]
Message-ID: <41FFB816.1070904@f-m.fm> (raw)
In-Reply-To: <20050128100238.27631.qmail@web606.mail.yahoo.co.jp>
ning wrote:
>Hello,Vitaly
>
>Thanks for your reply.
>
>I added SCC4 to rs_table as following:
>static struct serial_state rs_table[] = {
> /* UART CLK PORT IRQ FLAGS NUM */
> { 0, 0, PROFF_SCC1, SIU_INT_SCC1, 0, (0 |
>NUM_IS_SCC) }, /* SCC1 ttyS0 */
> { 0, 0, PROFF_SCC4, SIU_INT_SCC4, 0, (3 |
>NUM_IS_SCC) }, /* SCC4 ttyS1 */
>};
>
>ttyS0,ttyS1 work as COM port,but linux boot log only is
>outputed at ttyS0,how can I redirect it at ttyS1?
>After linux boots successfully,linux prompt will display
>at ttyS1,and I use it normally.
>(u-boot parameter: setenv bootargs root=/dev/nfs rw
>console=ttyS1,115200n8
>rootfs: /dev/console --> ttyS1)
>
>at \arch\ppc\boot\simple\m8260_tty.c,Even if I define
>SCC_CONSOLE to 4,Linux boot log is outputed at ttyS0.
>the following comment is written at m8260_tty.c:
>
>/* If defined, enables serial console. The value (1
>through 4) should designate which SCC is used, but this
>isn't complete. Only SCC1 is known to work at this time.
>*/
>
>#ifdef CONFIG_SCC_CONSOLE
>#define SCC_CONSOLE 4
>#endif
>
>
>Maybe it is true.
>
>
Well, I can only advice to try linuxppc_2_4 or -2.4 repositories, adding
bits to support SCC4 console and so on...
--
Regards,
Vitaly
next prev parent reply other threads:[~2005-02-01 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 8:27 Serial console problem on MPC8272ADS board Vitaly Bordug
2005-01-28 10:02 ` ning
2005-02-01 17:10 ` Vitaly Bordug [this message]
2005-02-02 12:28 ` Jeff Angielski
-- strict thread matches above, loose matches on Subject: below --
2005-01-23 8:56 ning
2005-01-24 18:28 ` annamaya
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=41FFB816.1070904@f-m.fm \
--to=vitaly_@f-m.fm \
--cc=linuxppc-embedded@ozlabs.org \
--cc=ningmin@yahoo.co.jp \
/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).