From: Wolfgang Denk <wd@denx.de>
To: Daris A Nevil <dnevil@snmc.com>
Cc: ?????? <engineersong@hanmail.net>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: SCC3 console problem on MPC860
Date: Fri, 30 Mar 2001 17:37:46 +0200 [thread overview]
Message-ID: <20010330153751.EE41228827@denx.denx.de> (raw)
In-Reply-To: Your message of "Fri, 30 Mar 2001 08:57:07 MDT." <3AC49EC3.978D9A4A@snmc.com>
In message <3AC49EC3.978D9A4A@snmc.com> you wrote:
>
> I had problems trying to get the uart.c driver to do what you wanted as
> well. I don't think it was really meant to support both SCC and SMC at
> the same time. I ended up splitting the driver into two different
I cannot verify this problem.
> drivers, making one work just for the SCC, and the other only for the
> SMC. This works quite well.
This is really not needed.
We have tested the normal uart driver in a setup running on 5 serial
ports (2 x SMC, 3 x SCC, with Ethernet of the 4th SCC). No serious
load tests so far, but basic I/O functions worked without any
problems.
> The code is in the QSLinux release, which you can download from
> ftp:://qslinux.org. When you untar the kernel you can find the two
> drivers in the directory snmc/qslinux/kernel/drivers/char.
Ummm... AFAIK QSLinux is based on a 2.2.5 kernel? That's _awfully_
old. I can imagine that there were lots of problems with the uart
driver at this time. And other bugs as well.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"How is this place run - is it an anarchy?"
"No, I wouldn't say so; it is not that well organised..."
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-03-30 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-30 0:58 SCC3 console problem on MPC860 ??????
2001-03-30 7:53 ` Wolfgang Denk
2001-03-30 14:57 ` Daris A Nevil
2001-03-30 15:37 ` Wolfgang Denk [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=20010330153751.EE41228827@denx.denx.de \
--to=wd@denx.de \
--cc=dnevil@snmc.com \
--cc=engineersong@hanmail.net \
--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).