All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Dave Airlie <airlied@gmail.com>, Ben Hutchings <ben@decadent.org.uk>
Cc: David Airlie <airlied@linux.ie>,
	linux-pci@vger.kernel.org, dri-devel@lists.sourceforge.net,
	Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [PATCH] agpgart: Reprobe VGA devices when a new GART device is added
Date: Mon, 01 Mar 2010 08:19:02 -0800	[thread overview]
Message-ID: <874ol0c8w9.fsf@pollan.anholt.net> (raw)
In-Reply-To: <21d7e9971003010033t1ec38beem5c79d18e79ac406c@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1376 bytes --]

On Mon, 1 Mar 2010 18:33:14 +1000, Dave Airlie <airlied@gmail.com> wrote:
> On Sun, Feb 28, 2010 at 1:30 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> > This addresses <http://bugzilla.kernel.org/show_bug.cgi?id=15021>.
> >
> > DRM drivers may fail to probe their devices when the associated AGP
> > GART does not yet have a driver, so we reprobe unbound VGA devices
> > when a GART device is added.
> >
> > Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> > ---
> > This is intended to address the dependency problem highlighted in the
> > above bug report.  That specific bug can be fixed by adding a module
> > dependency from i915 to intel_agp, but in general there is no fixed
> > relationship betweem DRM and GART drivers.
> >
> > There is a narrow race between the check for a current driver binding
> > and the call to device_reprobe().  This could be closed by adding a
> > variant on device_attach() and device_reprobe() that is a no-op for
> > bound devices.
> >
> 
> This isn't useful, generally there is no AGP binding, and most drivers
> if they can't find an AGP backend will still run fine without it. i.e. radeon,
> mga etc.
> 
> Intel is a special case and I think we've already merged an explicit
> depend.
> 
> Just build agp drivers into the kernel, I'm tempted to make them all
> non-modular.

That seems easier.

[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 345 bytes --]

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

[-- Attachment #3: Type: text/plain, Size: 161 bytes --]

--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

  reply	other threads:[~2010-03-01 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-28  3:30 [PATCH] agpgart: Reprobe VGA devices when a new GART device is added Ben Hutchings
2010-02-28 13:53 ` Ben Hutchings
2010-03-01  8:33 ` Dave Airlie
2010-03-01 16:19   ` Eric Anholt [this message]
2010-03-01 17:40     ` Ben Hutchings

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=874ol0c8w9.fsf@pollan.anholt.net \
    --to=eric@anholt.net \
    --cc=airlied@gmail.com \
    --cc=airlied@linux.ie \
    --cc=ben@decadent.org.uk \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=gregkh@suse.de \
    --cc=linux-pci@vger.kernel.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 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.