All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Luther <sl@bplan-gmbh.de>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: Andrew Morton <akpm@osdl.org>, Sven Luther <sl@bplan-gmbh.de>,
	linuxppc-dev@ozlabs.org
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: Mon, 31 Oct 2005 22:21:28 +0100	[thread overview]
Message-ID: <20051031212128.GA32116@localhost.localdomain> (raw)
In-Reply-To: <20051031190524.GE5055@mag.az.mvista.com>

On Mon, Oct 31, 2005 at 12:05:24PM -0700, Mark A. Greer wrote:
> 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?
> 
> It does have a PIC, DMA engine, and SRAM that Sven mentioned but there
> are also a serial controller (MPSC), an i2c controller, and a watchdog
> timer.  I would guess that the MPSC and i2c drivers, at least, should
> use MODULE_DEVICE_TABLE.  If you agree, I'll add it to the list.

Yeah, forgot those, we don't use them on the pegasos though. 

Friendly,

Sven Luther

  reply	other threads:[~2005-10-31 21:24 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
2005-10-31 19:05   ` Mark A. Greer
2005-10-31 21:21     ` Sven Luther [this message]
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=20051031212128.GA32116@localhost.localdomain \
    --to=sl@bplan-gmbh.de \
    --cc=akpm@osdl.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mgreer@mvista.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 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.