On Sun, Feb 06, 2005 at 12:58:46AM -0500, Jon Smirl wrote:
> On Sat, 5 Feb 2005 23:05:26 -0500, Dave Jones <[EMAIL PROTECTED]> wrote:
> > Take a peek at 'lspci -vv' output. You'll notice that the AGP
> > capabilities are attached to the host bridge.
>
> I see that now, why is it on the host bridge instead of the AGP
> bridge?
Not sure. Maybe its partly due to the host bridge having all the
smarts to deal with the memory controller.
> So that means if we add drivers for the host bridges we have
> to add the code to the AGP drivers. It also implies that we have to
> load them.
Why exactly are you trying to write host bridge drivers anyway ?
Confused.
If there's a sensible reason for such drivers, we could at some
stage have the bridge drivers check for AGP capabilities, and
if found, start up the initialisation of the relevant AGP chipset
driver. (and then rip out the whole PCI detection stuff in agpgart).
This is quite a lot of work though, so unless there's a really
compelling reason, I don't think its worth doing.
Another way forward (somewhat hacky in one sense, but a lot cleaner in another)
would be to change the PCI code so that it'll load and init
multiple drivers that claim to support the same PCI ID.
This may cause issues for some other drivers however where
we have an old and a new driver with ID overlap.
So,.. what are you up to?
Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
