From: Wolfgang Denk <wd@denx.de>
To: shagitgy@t2.technion.ac.il
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: UART on SCC2
Date: Wed, 26 Nov 2003 10:28:29 +0100 [thread overview]
Message-ID: <20031126092834.AF1C5C5F5F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 26 Nov 2003 11:20:48 +0200." <1069838448.3fc47070b587b@webmail.technion.ac.il>
In message <1069838448.3fc47070b587b@webmail.technion.ac.il> you wrote:
>
> Does anyone know the status of scc2 in uart.c?
> How far is it from working?
It's working fine for us both on 8xx and 82xx systems.
Best regards,
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've finally learned what `upward compatible' means. It means we get
to keep all our old mistakes." - Dennie van Tassel
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-26 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 9:20 UART on SCC2 shagitgy
2003-11-26 9:28 ` Wolfgang Denk [this message]
[not found] <1069840245.3fc47775c9a38@webmail.technion.ac.il>
2003-11-26 10:26 ` Wolfgang Denk
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=20031126092834.AF1C5C5F5F@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=shagitgy@t2.technion.ac.il \
/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).