linux-kernel - Re: modular intel-agp does not work on my box

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]

Message-ID: <20080222041921.GD21061@codemonkey.org.uk>
Date:	Thu, 21 Feb 2008 23:19:21 -0500
From:	Dave Jones <davej@...emonkey.org.uk>
To:	Gabriel C <nix.or.die@...glemail.com>
Cc:	Dave Airlie <airlied@...ux.ie>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Gabriel C <crazy@...galware.org>
Subject: Re: modular intel-agp does not work on my box

On Fri, Feb 22, 2008 at 04:27:33AM +0100, Gabriel C wrote:
 > Gabriel C wrote:
 > > Dave Airlie wrote:
 > >>> Hi,
 > >>>
 > >>> When building agp* modular ( CONFIG_AGP=y/m and CONFIG_AGP_INTEL=m ) intel-agp does nothing on my box 
 > >>> ( Dell Precision WorkStation 530 MT ) chipset is not being detected.
 > >>>
 > >>> Building both Y fixes that and agpgart works and also detects my chipset.
 > >> Have you got EDAC modules built as well? they might be taking ownership 
 > >> when they shouldn't..
 > >>
 > > 
 > > Yes I have EDAC built modular. I will build latest git without EDAC and agp modular
 > > and let you know if that fixes ( workarounds ;) ) the problem.
 > 
 > You are right without EDAC built , agp modular does work fine. I'm on 2.6.25-rc2-00477-g1a4c6be right now.
 > 
 > So it is an EDAC bug ?
 
No, it's a failing of the pci driver model. It currently doesn't
allow more than one driver to be bound to a single PCI device.
For multi-function devices like bridges, this means we see problems
like the one you mention.

	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/