From: Sven Luther <sl@bplan-gmbh.de>
To: Paul Mackerras <paulus@samba.org>
Cc: Andrew Morton <akpm@osdl.org>,
linuxppc-dev@ozlabs.org, Sven Luther <sl@bplan-gmbh.de>
Subject: Re: [PATCH 2.6.14-rc5 1/1] : mv643xx_eth_pcidev - implements hotplug for the marvell gige functionality by probing the northbridge pci id.
Date: Sat, 29 Oct 2005 07:37:49 +0200 [thread overview]
Message-ID: <20051029053749.GA874@localhost.localdomain> (raw)
In-Reply-To: <17251.265.196352.234376@cargo.ozlabs.ibm.com>
On Sat, Oct 29, 2005 at 02:56:41PM +1000, Paul Mackerras wrote:
> Sven Luther writes:
>
> > +static struct pci_device_id pci_marvell_mv64360[] = {
> > + { PCI_DEVICE(PCI_VENDOR_ID_MARVELL, PCI_DEVICE_ID_MARVELL_MV64360) },
>
> Are there other devices in this northbridge whose drivers might also
> want to bind to this PCI id?
>
> What other devices does this northbridge contain?
Yep, Dale proposed to add :
+ { PCI_DEVICE(PCI_VENDOR_ID_MARVELL, PCI_DEVICE_ID_MARVELL_MV64460) },
Which i was about to resubmit the patch when i saw the commit, ... Err, no i
misunderstood your question.
Other devices, well, there is the interrupt controller, some dma engine and
the builtin sram, but nothing to my knowledge which would benefit from being
bound to the pci id.
Friendly,
Sven Luther
next prev parent reply other threads:[~2005-10-29 5:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 7:51 [PATCH 2.6.14-rc5 1/1] : mv643xx_eth_pcidev - implements hotplug for the marvell gige functionality by probing the northbridge pci id Sven Luther
2005-10-25 18:24 ` Dale Farnsworth
2005-10-25 20:20 ` Sven Luther
2005-10-27 19:26 ` Christoph Hellwig
2005-10-27 19:57 ` Sven Luther
2005-10-27 21:14 ` Nicolas DET
2005-10-29 4:56 ` Paul Mackerras
2005-10-29 5:37 ` Sven Luther [this message]
2005-10-31 19:05 ` Mark A. Greer
2005-10-31 21:21 ` Sven Luther
2005-11-01 9:25 ` Paul Mackerras
2005-11-01 16:57 ` Mark A. Greer
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=20051029053749.GA874@localhost.localdomain \
--to=sl@bplan-gmbh.de \
--cc=akpm@osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.