From: Dave Jones <davej@codemonkey.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Gabriel C <nix.or.die@googlemail.com>,
Dave Airlie <airlied@linux.ie>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Gabriel C <crazy@frugalware.org>,
Doug Thompson <dougthompson@xmission.com>
Subject: Re: modular intel-agp does not work on my box
Date: Sat, 23 Feb 2008 13:14:14 -0500 [thread overview]
Message-ID: <20080223181414.GA24313@codemonkey.org.uk> (raw)
In-Reply-To: <20080223000355.42219a89.akpm@linux-foundation.org>
On Sat, Feb 23, 2008 at 12:03:55AM -0800, Andrew Morton wrote:
> > > 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.
>
> Well that sounds pretty bad. What will distros do about this?
either
* ship both modular, and let the user decide which one he wants.
* build just one of them (typically agp)
* build them both, and let the above bug happen
* build agp into the kernel, and edac modular, breaking edac
for a minority.
> Is there something short-term-and-sleazy we can do to "fix" it?
not that I'm aware of. I think Greg has been working on a long-term fix.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2008-02-23 18:14 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
2008-02-23 8:03 ` Andrew Morton
2008-02-23 18:14 ` Dave Jones [this message]
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=20080223181414.GA24313@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=crazy@frugalware.org \
--cc=dougthompson@xmission.com \
--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.