From: Dan Malek <dan@netx4.com>
To: Steve Tarr <tarr@lucent.com>
Cc: "Kim, Jin Young" <jykim@ce.cnu.ac.kr>,
Linux PPC Mailing List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: pci bridge in 8260
Date: Sat, 08 Jul 2000 14:01:40 -0400 [thread overview]
Message-ID: <39676C84.A63FD6F9@embeddededge.com> (raw)
In-Reply-To: 3967600B.92648EB6@lucent.com
Steve Tarr wrote:
>
> My understanding is not to expect it any time soon (<12months).
> As to a good alternative, I have no experience
Well, its a standard 60x bus. Anything that worked on those should
work on the 8260. I have seen/used 8260s with Tundra PowerSpan......
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-08 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-07 9:01 How to debug the linux kernel? Gong Zhuo
2000-07-07 10:37 ` Murray Jensen
2000-07-07 16:58 ` Tom Roberts
2000-07-08 1:07 ` pci bridge in 8260 Kim, Jin Young
2000-07-08 17:08 ` Steve Tarr
2000-07-08 18:01 ` Dan Malek [this message]
2000-07-08 0:27 ` How to debug the linux kernel? Graham Stoney
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=39676C84.A63FD6F9@embeddededge.com \
--to=dan@netx4.com \
--cc=jykim@ce.cnu.ac.kr \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=tarr@lucent.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).