From: Dan Malek <dan@embeddededge.com>
To: Jim Rowe <rowejames@acmsystems.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MPC8250 + PCMCIA + airo_cs card + IO Port mapping proble
Date: Fri, 23 May 2003 17:45:28 -0400 [thread overview]
Message-ID: <3ECE9678.2040506@embeddededge.com> (raw)
In-Reply-To: 1053728074.29793.30.camel@kneedragger
Jim Rowe wrote:
> ....It would be even better if you are
> using an MPC82xx chip with an integrated PCI controller.
Take a look at the 8245 with the integrated MPC10x PCI bridge.
Basically, the Sandpoint port. The 8250 is a more simple
implementation than this. The 405GP/Walnut would also be
a good example, just don't get mired in the details that it
doesn't have BATs :-)
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-23 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5.1.0.14.2.20030522143346.04b7e260@falcon.si.com>
2003-05-23 4:01 ` MPC8250 + PCMCIA + airo_cs card + IO Port mapping proble Jim Rowe
2003-05-23 22:14 ` Jim Rowe
2003-05-23 21:45 ` Dan Malek [this message]
2003-05-23 22:44 ` 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=3ECE9678.2040506@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rowejames@acmsystems.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).