linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Cox <adrian@humboldt.co.uk>
To: Ron Bianco <ronb@junction.net>
Cc: bhupinder sahran <bhup_sah@yahoo.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: 21554 device driver
Date: Sat, 04 Aug 2001 09:19:36 +0100	[thread overview]
Message-ID: <3B6BB018.6070900@humboldt.co.uk> (raw)
In-Reply-To: 000301c11c78$80e43fe0$4d012ac7@warp-speed


Ron Bianco wrote:
> However, the 8240 is able to handle up to 5 pci devices on it's own and has an internal arbiter.
> 66Mhz PCI too in some configurations.
> Therefore I'm curious about the fact that you apparently want to interface to more than 5 PCI devices.
> Is this correct?  Seems extreme for an embedded system.


As mentioned in the original post, the 21554 is a non-transparent PCI
bridge. This is normally used to make a device such as an 8240 into a
peripheral of a workstation or server.

In answer to the original question on drivers for the 21554, such code
is generally application dependent. I've been thinking of writing a
general framework for non-transparent bridging, but at the moment
nothing exists. So the first thing you need to do is decide on the
protocol between the applications on each side of the bridge. If the
protocol is IP, then there's code you'll be able to use as a starting
point, such as Montavista's Hard Hat Net:

http://www.mvista.com/products/hardhat.html

--
Adrian Cox   http://www.humboldt.co.uk/


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-08-04  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-03 23:37 21554 device driver bhupinder sahran
2001-08-04  0:00 ` Ron Bianco
2001-08-04  8:19   ` Adrian Cox [this message]

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=3B6BB018.6070900@humboldt.co.uk \
    --to=adrian@humboldt.co.uk \
    --cc=bhup_sah@yahoo.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=ronb@junction.net \
    /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).