From: Jon Smirl <jonsmirl@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>, Jon Smirl <jonsmirl@gmail.com>,
Matthew Wilcox <matthew@wil.cx>, Jesse Barnes <jbarnes@sgi.com>,
linux-pci@atrey.karlin.mff.cuni.cz,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: Patch to control VGA bus routing and active VGA device.
Date: Mon, 24 Jan 2005 18:11:37 -0500 [thread overview]
Message-ID: <9e4733910501241511d0d91b4@mail.gmail.com> (raw)
In-Reply-To: <20050124195523.B5541@flint.arm.linux.org.uk>
On Mon, 24 Jan 2005 19:55:23 +0000, Russell King
<rmk+lkml@arm.linux.org.uk> wrote:
> There's a very good reason not to have a bridge driver at the moment -
> some PCI to PCI bridges need special drivers. Currently, as the device
> model stands today, we can only have ONE PCI to PCI bridge driver for
> all P2P bridges, which is bad news if you need a specific driver for,
> eg, a mobility docking station P2P bridge.
There is no requirement that the bridge driver be generic code. I
agree that it is simpler but there is nothing stopping a "generic"
driver from just having PCI IDs for all of the existing bridges built
into it and then load it like a normal driver. Loading all of the
bridge PCI IDs into the "generic" driver gets rid of the need for
driver priorities.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-01-24 23:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 3:43 Patch to control VGA bus routing and active VGA device Jon Smirl
2005-01-18 17:46 ` Jesse Barnes
2005-01-18 19:38 ` H. Peter Anvin
2005-01-18 21:06 ` Jesse Barnes
2005-01-22 19:04 ` Jon Smirl
2005-01-24 17:25 ` Jesse Barnes
2005-01-24 17:53 ` Jesse Barnes
[not found] ` <41ED3BD2.1090105@pobox.com>
[not found] ` <9e473391050122083822a7f81c@mail.gmail.com>
[not found] ` <200501240847.51208.jbarnes@sgi.com>
[not found] ` <20050124175131.GM31455@parcelfarce.linux.theplanet.co.uk>
2005-01-24 19:17 ` Fwd: " Jon Smirl
2005-01-24 19:42 ` Jeff Garzik
2005-01-24 19:55 ` Russell King
2005-01-24 23:11 ` Jon Smirl [this message]
2005-01-25 4:24 ` Greg KH
2005-01-27 9:59 ` Jon Smirl
2005-01-27 16:28 ` Jesse Barnes
2005-01-28 17:32 ` Grant Grundler
2005-01-28 18:36 ` Jon Smirl
2005-01-28 19:15 ` Grant Grundler
2005-01-28 19:26 ` Jon Smirl
2005-01-28 19:34 ` Grant Grundler
2005-01-28 18:41 ` Jesse Barnes
2005-01-28 19:33 ` Grant Grundler
2005-01-28 19:41 ` Jesse Barnes
2005-01-28 20:12 ` Grant Grundler
2005-01-28 20:00 ` Matthew Wilcox
2005-01-28 20:07 ` Russell King
2005-01-31 16:01 ` Alan Cox
2005-02-01 6:38 ` Greg KH
2005-02-01 16:24 ` Jon Smirl
2005-01-30 7:51 ` Jon Smirl
2005-01-24 20:14 ` Matthew Wilcox
2005-01-24 20:22 ` Matthew Wilcox
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=9e4733910501241511d0d91b4@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=jbarnes@sgi.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=matthew@wil.cx \
/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.