linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ira Snyder <iws@ovro.caltech.edu>
Cc: Ayman El-Khashab <AymanE@tanisys.com>, linuxppc-dev@ozlabs.org
Subject: Re: Help enabling PCI endpoint on 460EX, host sees disabled
Date: Thu, 11 Dec 2008 22:04:28 +1100	[thread overview]
Message-ID: <1228993468.22413.165.camel@pasglop> (raw)
In-Reply-To: <20081211001758.GA29190@ovro.caltech.edu>

On Wed, 2008-12-10 at 16:17 -0800, Ira Snyder wrote:
> On Wed, Dec 10, 2008 at 05:29:53PM -0600, Ayman El-Khashab wrote:
> > My system consists of a pair of 460EXs attached by way of both PCI-E and
> > PCI.  Ultimately my goal is to communicate between them via pci-e (is
> > there anything out there that does this already?).
> 
> I can't help you with that exact board, but I've written an "ethernet
> over PCI" driver for Linux and U-Boot. The Linux driver has been posted
> here on linuxppc-dev and on the lkml. Search for "net: add PCINet
> driver" and you'll find it.
> 
> It won't work on your board, but it should serve as a good example about
> how to communicate over PCI.
> 
> You are the third user asking for something like this recently. :) Too
> bad the mainline kernel developers seem to be mostly ignoring the
> driver I wrote.

Don't get too disappointed... a lot of us are busy and things fall
through the cracks.. it may just be that we had nothing bad to say about
it :-)

Seriously, if you feel you didn't get useful reviews or that nothing is
picking it up, just holler, and nag us. We all have pretty full plates
and things do slip or just forgotten :-)

Cheers,
Ben.

  parent reply	other threads:[~2008-12-11 11:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 23:29 Help enabling PCI endpoint on 460EX, host sees disabled Ayman El-Khashab
2008-12-11  0:17 ` Ira Snyder
2008-12-11  2:13   ` Ayman El-Khashab
2008-12-11 11:04   ` Benjamin Herrenschmidt [this message]
2008-12-11 16:22     ` Ira Snyder
2008-12-11 22:40       ` Benjamin Herrenschmidt

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=1228993468.22413.165.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=AymanE@tanisys.com \
    --cc=iws@ovro.caltech.edu \
    --cc=linuxppc-dev@ozlabs.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).