From: Dave Jones <davej@codemonkey.org.uk>
To: Gabriel C <nix.or.die@googlemail.com>
Cc: Dave Airlie <airlied@linux.ie>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Gabriel C <crazy@frugalware.org>
Subject: Re: modular intel-agp does not work on my box
Date: Thu, 21 Feb 2008 23:19:21 -0500 [thread overview]
Message-ID: <20080222041921.GD21061@codemonkey.org.uk> (raw)
In-Reply-To: <47BE4125.3080503@googlemail.com>
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
next prev parent reply other threads:[~2008-02-22 4:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 1:15 modular intel-agp does not work on my box Gabriel C
2008-02-22 2:06 ` Dave Airlie
2008-02-22 2:26 ` Gabriel C
2008-02-22 3:27 ` Gabriel C
2008-02-22 4:19 ` Dave Jones [this message]
2008-02-23 8:03 ` Andrew Morton
2008-02-23 18:14 ` Dave Jones
2008-02-23 19:30 ` Gabriel C
2008-02-23 19:45 ` 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=20080222041921.GD21061@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=airlied@linux.ie \
--cc=crazy@frugalware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@googlemail.com \
/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.