From: Matt Domsch <Matt_Domsch@dell.com>
To: Dave Jones <davej@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: intel-agp: skip non-AGP devices
Date: Tue, 8 Jun 2004 11:00:27 -0500 [thread overview]
Message-ID: <20040608160027.GA13214@lists.us.dell.com> (raw)
In-Reply-To: <20040601163100.GC1265@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
On Tue, Jun 01, 2004 at 05:31:00PM +0100, Dave Jones wrote:
> On Tue, Jun 01, 2004 at 05:20:58PM +0100, Christoph Hellwig wrote:
>
> > > The patch below checks for a valid cap_ptr prior to printing the
> > > message, now at KERN_WARNING level (it's not really an error, is it?)
> >
> > The real problem is that agpgart doesn't properly fill in the pci_id
> > table but claims all devices and then does it's own probing internally.
> > This also breaks hotplug in a funny way.
>
> This is fixed in agpgart-bk / -mm. Andi went through all the drivers
> adding their id's. Should be going to Linus soon.
>
> Dave
FWIW, sworks-agp.c has the same issue in mainline yet today.
agpgart: Unsupported Serverworks chipset (device id: 0011)
agpgart: Unsupported Serverworks chipset (device id: 0201)
I'll look at -mm to verify it's fixed there.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-08 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 16:04 intel-agp: skip non-AGP devices Matt Domsch
2004-06-01 16:20 ` Christoph Hellwig
2004-06-01 16:31 ` Dave Jones
2004-06-08 16:00 ` Matt Domsch [this message]
2004-06-08 16:10 ` Dave Jones
2004-06-08 16:17 ` Matt Domsch
2004-06-08 16:25 ` Dave Jones
2004-06-08 16:44 ` Dave Jones
2004-06-01 16:24 ` Dave Jones
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=20040608160027.GA13214@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=davej@redhat.com \
--cc=hch@infradead.org \
--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 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.