From: Matt Domsch <Matt_Domsch@dell.com>
To: davej@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: intel-agp: skip non-AGP devices
Date: Tue, 1 Jun 2004 11:04:57 -0500 [thread overview]
Message-ID: <20040601160457.GA11437@lists.us.dell.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]
Dave,
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:
00:00.0 Host bridge: Intel Corp. E7501 Memory Controller Hub (rev 01)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Capabilities: [40] #09 [1105]
agp_intel_probe() calls pci_find_capability(PCI_CAP_ID_AGP)
but doesn't check the return value (should be zero in this case) prior
to moving into the switch.
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?)
Thoughts?
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
--- intel-agp.c.orig Tue Jun 1 10:45:59 2004
+++ intel-agp.c Tue Jun 1 11:02:56 2004
@@ -1382,8 +1382,9 @@ static int __devinit agp_intel_probe(str
name = "E7205";
break;
default:
- printk(KERN_ERR PFX "Unsupported Intel chipset (device id: %04x)\n",
- pdev->device);
+ if (cap_ptr)
+ printk(KERN_WARNING PFX "Unsupported Intel chipset (device id: %04x)\n",
+ pdev->device);
return -ENODEV;
};
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-06-01 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 16:04 Matt Domsch [this message]
2004-06-01 16:20 ` intel-agp: skip non-AGP devices 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
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=20040601160457.GA11437@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=davej@redhat.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 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.