From: "Mark A. Greer" <mgreer@mvista.com>
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: Tue, 1 Nov 2005 09:57:29 -0700 [thread overview]
Message-ID: <20051101165729.GA2987@mag.az.mvista.com> (raw)
In-Reply-To: <17255.13444.672360.996441@cargo.ozlabs.ibm.com>
On Tue, Nov 01, 2005 at 08:25:24PM +1100, Paul Mackerras wrote:
> Mark A. Greer writes:
>
> > 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.
>
> But the point is that if one driver has claimed the device (because
> its ID is in its module device table), the other drivers won't be able
> to.
Okay. TBH, I still have to look at what the MODULE_DEVICE_TABLE does so
it was ignorance + laziness on my part.
> You need something like the macio driver that BenH did, which
> claims the macio device and creates a macio bus structure and allows
> individual macio device drivers to claim the pieces of it.
I'll take a look.
Mark
prev parent reply other threads:[~2005-11-01 16:57 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
2005-11-01 9:25 ` Paul Mackerras
2005-11-01 16:57 ` Mark A. Greer [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=20051101165729.GA2987@mag.az.mvista.com \
--to=mgreer@mvista.com \
--cc=akpm@osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sl@bplan-gmbh.de \
/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).