From: Dave Jones <davej@redhat.com>
To: Kevin Puetz <puetzk@puetzk.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.19-rc1][AGP] Regression - amd_k7_agp no longer detected
Date: Tue, 12 Dec 2006 13:06:46 -0500 [thread overview]
Message-ID: <20061212180646.GF2140@redhat.com> (raw)
In-Reply-To: <loom.20061211T025904-121@post.gmane.org>
On Mon, Dec 11, 2006 at 02:06:19AM +0000, Kevin Puetz wrote:
> Shawn Starr <shawn.starr <at> rogers.com> writes:
>
> >
> > On Friday 06 October 2006 2:08 am, Dave Jones wrote:
> > > On Fri, Oct 06, 2006 at 01:50:19AM -0400, Shawn Starr wrote:
> > > > When loading amd_k7_agp nothing appears from kernel, no information
> > > > about the AGP chipset/aptreture size etc. Even putting kprints inside
> > > > the probe() function of the driver does not get called.
> > >
> > > Even as the first thing in agp_amdk7_probe() ?
> > ... (http://thread.gmane.org/gmane.linux.kernel/453869)
>
> I'm hitting this problem too, and as it's still present in the 2.6.19 final, I'm
> assuming you never got enough information to chase it. I found the following
> note in the debian BTS that seems relevant:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=363682
>
> I can confirm that if I remove the amd76x_edac module and reload amd_k7_agp, it
> detects the aperture. If I then reload radeon.ko and X, I get DRI (and AIGLX).
> So hopefully that's a lead to what might have changed...
This is increasingly becoming a problem. For cases where we have >1 driver
trying to 'own' a single PCI ID, the first to init generally wins.
Similar problems exist with intel agp vs edac, intel agp vs intel watchdog,
matroxfb vs W1, and probably more..
What's needed is a governing module that claims the device and arbitrates
for drivers 'below' it.
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2006-12-12 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 5:50 [2.6.19-rc1][AGP] Regression - amd_k7_agp no longer detected Shawn Starr
2006-10-06 6:08 ` Dave Jones
2006-10-06 6:59 ` Shawn Starr
2006-12-11 2:06 ` Kevin Puetz
2006-12-12 18:06 ` Dave Jones [this message]
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=20061212180646.GF2140@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=puetzk@puetzk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox