From: Russell King <rmk@arm.linux.org.uk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Mark Haverkamp <markh@osdl.org>, Patrick Mochel <mochel@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pci bridge class code
Date: Mon, 2 Jun 2003 13:32:58 +0100 [thread overview]
Message-ID: <20030602133258.A776@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1054554964.535.35.camel@gaston>; from benh@kernel.crashing.org on Mon, Jun 02, 2003 at 01:56:04PM +0200
On Mon, Jun 02, 2003 at 01:56:04PM +0200, Benjamin Herrenschmidt wrote:
> On Fri, 2003-05-30 at 11:44, Alan Cox wrote:
>
> > The same is true of serveral hot docking bridges such as the one on the
> > IBM TP600 and also of other devices which happen to be both a PCI-PCI
> > bridge and have other magic stuck on them.
>
> Maybe we could find some way to prioritize matching ? It's a bit late now,
> but well... if the match functions returned an integer, 0 beeing lower match,
> we could have some kind of prioritization.
>
> That way, a class match would have lower priority than a vendorID/deviceID
> match, etc...
That would not help the case when you have the "generic" bridge module
loaded and the specific bridge driver as a loadable module.
--
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-06-02 12:19 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
2003-05-30 9:44 ` Alan Cox
2003-06-02 11:56 ` Benjamin Herrenschmidt
2003-06-02 12:32 ` Russell King [this message]
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=20030602133258.A776@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--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