From: "Allen Curtis" <acurtis@onz.com>
To: "Sylvain Latulippe" <slatulippe@mediatrix.com>,
"'Michael Thompson'" <mickey@berkeley.innomedia.com>,
<linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Are 8260 and 8250 CPM interface compatible?
Date: Fri, 27 Sep 2002 06:25:13 -0700 [thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFGEJJDMAA.acurtis@onz.com> (raw)
In-Reply-To: <2702075D4DE2B043BF5EB82E9CFAD45B0CAD26@mail1.mediatrix.com>
> We have tested ethernet (fcc_enet.c), serial port (uart.c) from
> linux 2.4.19
> and it works fine.
Considering that Motorola is now using the CPM in multiple processors, including DSPs, would it make sense to breakout the support from the 8260 implementation and make it an independent option like PCI?
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-09-27 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 12:29 Are 8260 and 8250 CPM interface compatible? Sylvain Latulippe
2002-09-27 13:25 ` Allen Curtis [this message]
2002-09-27 15:53 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2002-09-27 4:47 Michael Thompson
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=NCBBIINEHIPFGJPLBEIFGEJJDMAA.acurtis@onz.com \
--to=acurtis@onz.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mickey@berkeley.innomedia.com \
--cc=slatulippe@mediatrix.com \
/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).