From: Wolfgang Denk <wd@denx.de>
To: "Björn Östby" <Bjorn.Ostby@combitech.se>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 8xx SMC1 problem
Date: Thu, 16 Mar 2006 21:10:03 +0100 [thread overview]
Message-ID: <20060316201003.9522F353B16@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 16 Mar 2006 18:23:46 +0100." <004B1D7A5257174C9044A1B7BD0E60ED0178CC68@ratatosk.combitechsystems.com>
In message <004B1D7A5257174C9044A1B7BD0E60ED0178CC68@ratatosk.combitechsystems.com> you wrote:
>
> First of, I have three serial ports (SMC1, SMC2 and SCC3) and they all work
> fine when the console is on SMC1. I have gadgets connected to SMC2 and SCC
> 3 and now I need SMC1 for yet another device. So I have undefined CONFIG_SE
> RIAL_CONSOLE in the kernel config and I jump out of u-boot (which have the
> console on SMC1) with the argument "console=none".
And did you make sure that no other process is accessing ttyS0 ?
> When logging in (via telnet) ttyS0 works no more (but S1 and S2 does). At r
> andom bootups, it is possible to open the port but it is no good for read o
> r write.
>
> Can anybody give me some advise on how to enable SMC1 but at the same time
> don't have a console on it?
We did the same (passing console=null) in a couple of configurations
and had no problems using SMC1 as standard serial port. Try *not*
undefining CONFIG_SERIAL_CONSOLE.
And please keep your line length < 72 characters or so.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
A committee is a life form with six or more legs and no brain.
-- Lazarus Long, "Time Enough For Love"
next prev parent reply other threads:[~2006-03-16 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 17:23 8xx SMC1 problem Björn Östby
2006-03-16 20:10 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-17 6:55 Björn Östby
2006-03-17 15:25 ` Antonio Di Bacco
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=20060316201003.9522F353B16@atlas.denx.de \
--to=wd@denx.de \
--cc=Bjorn.Ostby@combitech.se \
--cc=linuxppc-embedded@ozlabs.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).