From: Dave Jones <davej@redhat.com>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: intel-agp: skip non-AGP devices
Date: Tue, 1 Jun 2004 17:24:07 +0100 [thread overview]
Message-ID: <20040601162407.GB1265@redhat.com> (raw)
In-Reply-To: <20040601160457.GA11437@lists.us.dell.com>
On Tue, Jun 01, 2004 at 11:04:57AM -0500, Matt Domsch wrote:
> On our PowerEdge 2600 system, which has an Intel E7501 Memroy
> Controller Hub, the intel-agp probe code is reporting, at KERN_ERR no less:
>
> agpgart: Unsupported Intel chipset (device id 254c)
>
> Now, of course it says this, as this device does not present itself as
> AGP-capable:
>
> 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?)
indeed, patch applied.
Thanks,
Dave
prev parent reply other threads:[~2004-06-01 16:26 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
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 [this message]
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=20040601162407.GB1265@redhat.com \
--to=davej@redhat.com \
--cc=Matt_Domsch@dell.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