From: Peter Ryser <Peter.Ryser@xilinx.com>
To: bob piatek <bobtek@fishcamp.com>
Cc: emanuel stiebler <emu@ecubics.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Virtex II Pro eval Boards
Date: Fri, 16 May 2003 17:22:18 -0700 [thread overview]
Message-ID: <3EC580BA.20CE27DC@xilinx.com> (raw)
In-Reply-To: 5668A00E-87FA-11D7-AD26-000393D6CBAE@fishcamp.com
> Xilinx has a OPB to PCI bridge that supports their PCI core but it
> doesn't (yet) support host applications.
Yes, it does. Many PCI, PCMCIA, and PC cards work.
- Peter
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-17 0:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 22:40 Virtex II Pro eval Boards emanuel stiebler
2003-05-16 23:58 ` bob piatek
2003-05-17 0:22 ` Peter Ryser [this message]
2003-05-17 0:42 ` bob piatek
2003-05-21 16:06 ` Peter Ryser
2003-05-21 16:43 ` bob piatek
2003-05-19 9:30 ` Peter Vandenabeele
2003-05-17 0:04 ` Peter Ryser
-- strict thread matches above, loose matches on Subject: below --
2003-05-16 22:42 Kerl, John
2003-05-17 0:11 Kerl, John
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=3EC580BA.20CE27DC@xilinx.com \
--to=peter.ryser@xilinx.com \
--cc=bobtek@fishcamp.com \
--cc=emu@ecubics.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).