From: Russell King <rmk@arm.linux.org.uk>
To: Mark Haverkamp <markh@osdl.org>
Cc: Pat Mochel <mochel@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pci bridge class code
Date: Thu, 29 May 2003 21:40:44 +0100 [thread overview]
Message-ID: <20030529214044.B30661@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1054239461.28608.74.camel@markh1.pdx.osdl.net>; from markh@osdl.org on Thu, May 29, 2003 at 01:17:42PM -0700
On Thu, May 29, 2003 at 01:17:42PM -0700, Mark Haverkamp wrote:
> This adds pci-pci bridge driver model class code. Entries appear in
> /sys/class/pci_bridge.
Hmm. Ok.
How do you propose to handle the following case:
Mobility Electronics supply a Cardbus to PCI bridged "docking station"
which has a PCI-PCI bridge on with vendor stuff above 0x40. It appears
as a standard PCI-PCI bridge; the only specific identifying information
are the device and vendor IDs. How can I guarantee that a driver I
write for this device will be picked up in preference to your driver.
(Given that your driver would probably be always loaded, and my driver
could well be a loadable module.)
I'm not saying that I will need to do this, but this is something which
needs to be carefully thought about if we're going to provide a generic
driver.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-05-29 20:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 20:17 [PATCH] pci bridge class code Mark Haverkamp
2003-05-29 20:40 ` Russell King [this message]
2003-05-30 9:44 ` Alan Cox
2003-06-02 11:56 ` Benjamin Herrenschmidt
2003-06-02 12:32 ` Russell King
2003-06-02 12:39 ` Benjamin Herrenschmidt
2003-06-02 14:25 ` Mark Haverkamp
2003-05-30 23:13 ` Greg KH
2003-06-02 20:30 ` Mark Haverkamp
2003-06-02 20:35 ` Greg KH
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=20030529214044.B30661@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@osdl.org \
--cc=mochel@osdl.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