From: Adrian Cox <apc@agelectronics.co.uk>
To: Pei-Jie Hong <Pei-Jie.Hong@cern.ch>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: PCI-to-PCI bridge 21554?
Date: Mon, 13 Nov 2000 14:56:45 +0000 [thread overview]
Message-ID: <3A10012D.DFA76093@agelectronics.co.uk> (raw)
In-Reply-To: 3A0FF521.D2358D7D@cern.ch
Pei-Jie Hong wrote:
> We are recently working on the PCI-to-PCI bridge 21554, which
> is a non-transparent bridge. But we have some problem with it. Does
> anyone on this list ever do something with this bridge. Thanks.
I've been working with this bridge for a few months now, using it with
an x86 PC on the primary side and a PowerPC SBC on the other. I've so
far set up address translations across it, and used the I2O unit without
any problems. What are you trying to do with the 21554, and what sort of
board is it on?
- Adrian Cox, AG Electronics
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-11-13 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 14:05 PCI-to-PCI bridge 21554? Pei-Jie Hong
2000-11-13 14:56 ` Adrian Cox [this message]
2000-11-13 17:45 ` Joe Green
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=3A10012D.DFA76093@agelectronics.co.uk \
--to=apc@agelectronics.co.uk \
--cc=Pei-Jie.Hong@cern.ch \
--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).