linux-kernel - Re: I815 suddenly unkown to agpgart?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Jun 2007 12:15:13 -0400
From:	Dave Jones <davej@...hat.com>
To:	Meelis Roos <mroos@...ux.ee>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Wang Zhenyu <zhenyu.z.wang@...el.com>,
	Eric Anholt <eric@...olt.net>
Subject: Re: I815 suddenly unkown to agpgart?

On Wed, Jun 13, 2007 at 12:01:52PM -0400, Dave Jones wrote:
 > On Wed, Jun 13, 2007 at 06:07:42PM +0300, Meelis Roos wrote:
 >  > agpgart: Unsupported Intel chipset(device id: 1130)
 > 
 > This is likely due to 9614ece14f23f2ce54a076c471aec9c91e51e79c
 > 
 >     [AGPGART] intel_agp: use table for device probe
 >     
 >     Fixed issues noted by Christoph Hellwig, and I changed device table
 >     scan a bit to allow the case that some models of graphics chips may
 >     have same host bridge type. This type of chip will be added in the future.
 >     
 >     This patch cleans up device probe function. Eric Anholt was the original author.
 > 
 > Eric ?

Oh, we have this check in find_gmch ..

        if (gmch_device && PCI_FUNC(gmch_device->devfn) != 0) {
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Which isn't going to work, as Meelis has a gmch on device0, slot0, devfn1.
Meelis, does it start working again if you change that to just

	if (gmch_Device) {

?

	Dave

-- 
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/