From: Wolfgang Denk <wd@denx.de>
To: Arun Dharankar <ADharankar@ATTBI.Com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Serial console ports on systems with no console connected.
Date: Mon, 22 Jul 2002 09:03:50 +0200 [thread overview]
Message-ID: <20020722070355.EC9F310874@denx.denx.de> (raw)
In-Reply-To: Your message of "Sun, 21 Jul 2002 15:10:36 EDT." <200207211510.36128.ADharankar@ATTBI.Com>
Dear Arun,
in message <200207211510.36128.ADharankar@ATTBI.Com> you wrote:
>
> The conclusion for my case is that the RTS/CTS. DSR/DTR and
> DCD need to be null modem'd. Working around by ignoring the
> flow control (as I mentioned in earlier port) also is workable for
> me because I know which port is the console, and we dont
> have a need for the other serial port for any other use.
This makes little sense to me.
You mentioned before that you're on a 8260, using SMC1 and SCC4 for
serial ports:
> The board has SCC4 and SMC1 based serial ports. I have
> tried both of these as console ports under Linux and PPCBOOT.
> PPCBOOT code is unmodified (as it is from the distribution) for
> SCC4 and SMC1 code. The Linux code is unmodified for
> SMC1, and I see this behavior in case of both these serial
> ports.
Well, I don;t know what you did to support SCC4 in the Linux UART
driver, and if you added HW flow control there. The standard driver
does not contain any HW flow control.
And the SMC port does not even provide a chance to implement HW flow
control since it has no handshake signals at all.
How can you null modem RTS/CTS, DSR/DTR and DCD signals if there
aren't any such signals on the port?
I'm confused.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
I am a computer. I am dumber than any human and smarter than any ad-
ministrator.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-07-22 7:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 22:08 Serial console ports on systems with no console connected Richard Williams
2002-07-09 23:45 ` Arun Dharankar
2002-07-10 6:47 ` Murray Jensen
2002-07-10 11:41 ` Jerry Van Baren
2002-07-11 1:53 ` Arun Dharankar
2002-07-21 19:10 ` Arun Dharankar
2002-07-22 7:03 ` Wolfgang Denk [this message]
[not found] <ADharankar@ATTBI.Com>
[not found] ` <200207252058.04074.ADharankar@ATTBI.Com>
2002-07-26 2:22 ` Murray Jensen
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 1:27 Arun Dharankar
2002-07-09 5:14 ` Wolfgang Denk
2002-07-09 12:08 ` Arun Dharankar
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=20020722070355.EC9F310874@denx.denx.de \
--to=wd@denx.de \
--cc=ADharankar@ATTBI.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).