From: Tom Roberts <tjroberts@lucent.com>
To: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Query: PCI and Ethernet hardware/drivers
Date: Fri, 26 Jan 2001 11:25:42 -0600 [thread overview]
Message-ID: <3A71B316.91C9EDBD@lucent.com> (raw)
In-Reply-To: 3A71946D.C98063EB@agelectronics.co.uk
Adrian Cox wrote:
> 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?
Nothing obscure, I hope. We need a local PCI bus to interface to
two ethernet MACs, some HDLC interfaces, and the H.110 telephony bus
(Lucent has a part which directly interfaces H.110 to PCI). While these
other devices will be PCI masters (for DMA), they are all quite dumb
and will be programmed from our 7410s (Linux).
> Does this mean that your board is intended to be a PCI agent?
I don't think so. There will be no other CPUs on the PCI bus, just
peripherals. But we want them to DMA into our big memory.
> > 4) We favor a 4-CPU SMP configuration. What not-so-obvious problems
> > are we likely to face?
> Designing a good interrupt controller.
We have done this for our current boards, but they have no PCI bus,
only local peripherals directly connected to a 60x or MAX bus. "good"
to us merely means it works reliably; we have only rather low data
rates as this is primarily a compute engine -- 200 kilobytes/sec
would be a high data rate to us (during boot it will be higher).
Thank you very much for your quick response.
Tom Roberts tjroberts@lucent.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-26 17:25 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
2001-01-26 17:25 ` Tom Roberts [this message]
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=3A71B316.91C9EDBD@lucent.com \
--to=tjroberts@lucent.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).