From: Adrian Cox <apc@agelectronics.co.uk>
To: Tom Roberts <tjroberts@lucent.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Query: PCI and Ethernet hardware/drivers
Date: Fri, 26 Jan 2001 15:14:53 +0000 [thread overview]
Message-ID: <3A71946D.C98063EB@agelectronics.co.uk> (raw)
In-Reply-To: 3A718D21.66F9227D@lucent.com
Tom Roberts wrote:
> 1) Does Linux/PPC handle the PCI bus properly?
Short answer, yes. Long answer, how strange a PCI system do you want to
build?
> 2) Are there Linux/PPC drivers for the PLX 9054 (PCI interface) chip?
> (Yes, that is PPC 60x-bus, not MAX bus; the hardware will handle that)
I ported the 2.2 kernel to a board which used the very similar PLX 9080.
Does this mean that your board is intended to be a PCI agent? If so,
you've got a whole world of fun ahead of you, and you can ask me for
more details.
> 3) What Ethernet MAC chips have people had success using?
> (right now we favor an AMD chip, which they claim has Linux drivers,
> but their test plan includes only AMD and Intel CPUs, not PowerPC)
I've used a fully integrated AMD part. Works fine, even if it's not the
world's cleverest ethernet chip.
> 4) We favor a 4-CPU SMP configuration. What not-so-obvious problems
> are we likely to face? (e.g. our simulations show that doing this
> at 133 MHz cannot be done using a CPLD-based memory controller:
> wimpy data-bus drivers (:-() Our existing boards are all non-SMP,
> and bus snooping is a bit of a mystery to us....
Designing a good interrupt controller.
- Adrian Cox
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-26 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 7:28 Problems with turn_on_mmu Subodh Nijsure
2001-01-26 8:14 ` Gabriel Paubert
2001-01-26 14:43 ` Query: PCI and Ethernet hardware/drivers Tom Roberts
2001-01-26 15:14 ` Adrian Cox [this message]
2001-01-26 17:25 ` Tom Roberts
2001-01-29 11:19 ` Adrian Cox
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=3A71946D.C98063EB@agelectronics.co.uk \
--to=apc@agelectronics.co.uk \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=tjroberts@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).