From: Rainer Kloud <rainer.kloud@siemens.at>
To: Julia Elbert <jelbert@enerdyne.com>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: uart.c and scc2
Date: Mon, 27 Nov 2000 19:05:26 +0100 [thread overview]
Message-ID: <3A22A266.68B77C68@siemens.at> (raw)
In-Reply-To: 67505026E29DD311A9AA00508B7315F350A5D1@EXCHANGE
Dear Julia,
> Does anyone know the status of scc2 in uart.c?
> How far is it from working?
I have done a quick port of the uart to SCC1 for my
Scout Board (MPC 8260, linux2.4.0-test4).
Because of other problems with my port for Scout
(and other running projects) I was not able to publish
this changes.
If you want to get the source file I can mail it to you.
Best Regards
Rainer
--
Rainer Kloud mailto:rainer.kloud@siemens.at
Siemens AG, PSE ECT OTN 2, Rampengasse 3-5, A-1190 Vienna
Phone: +43-(0)51707-43873 Fax: +43-(0)51707-53581
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
parent reply other threads:[~2000-11-27 18:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <67505026E29DD311A9AA00508B7315F350A5D1@EXCHANGE>]
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=3A22A266.68B77C68@siemens.at \
--to=rainer.kloud@siemens.at \
--cc=jelbert@enerdyne.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).