From: Dave Jones <davej@redhat.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Intel AGP support attaching to wrong PCI IDs
Date: Sun, 6 Feb 2005 01:08:40 -0500 [thread overview]
Message-ID: <20050206060839.GA19330@redhat.com> (raw)
In-Reply-To: <9e4733910502052158491b5ce3@mail.gmail.com>
On Sun, Feb 06, 2005 at 12:58:46AM -0500, Jon Smirl wrote:
> On Sat, 5 Feb 2005 23:05:26 -0500, Dave Jones <davej@redhat.com> 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
next prev parent reply other threads:[~2005-02-06 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 1:45 Intel AGP support attaching to wrong PCI IDs Jon Smirl
2005-02-06 4:05 ` Dave Jones
2005-02-06 5:58 ` Jon Smirl
2005-02-06 6:08 ` Dave Jones [this message]
1996-01-19 21:38 ` Maciej W. Rozycki
2005-02-06 6:49 ` Jon Smirl
2005-02-06 7:25 ` Kyle Moffett
2005-02-06 21:37 ` Ian Pilcher
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=20050206060839.GA19330@redhat.com \
--to=davej@redhat.com \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.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