public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Adam Jackson <ajax@redhat.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [BUG] intel_drv.so fails to load
Date: Wed, 18 Jul 2012 15:36:09 +0100	[thread overview]
Message-ID: <1342622195_12548@CP5-2952> (raw)
In-Reply-To: <1342621766.3590.29.camel@atropine>

On Wed, 18 Jul 2012 10:29:26 -0400, Adam Jackson <ajax@redhat.com> wrote:
> So those should resolve lazily, which means if you never call them they
> never _need_ to resolve.  And this is how X drivers normally work,
> notice that libfb isn't loaded _before_ you load your driver but yet the
> driver loads.

They were being used by i810_dri.c, so i810 was busted. It just happened
to be that the first user to spot this was not using i810.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2012-07-18 14:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 20:08 [BUG] intel_drv.so fails to load Knut Petersen
2012-07-17 20:16 ` Chris Wilson
2012-07-17 20:41   ` Chris Wilson
2012-07-17 20:54     ` Knut Petersen
2012-07-17 21:11       ` Adam Jackson
2012-07-17 21:34         ` Knut Petersen
2012-07-17 21:16       ` Chris Wilson
2012-07-17 21:52         ` Knut Petersen
2012-07-18 14:02         ` Adam Jackson
2012-07-18 14:07           ` Chris Wilson
2012-07-18 14:29             ` Adam Jackson
2012-07-18 14:36               ` Chris Wilson [this message]
2012-07-18 19:47                 ` Adam Jackson
2012-07-18 22:34                   ` Chris Wilson
2012-07-19 14:08                     ` Adam Jackson
2012-07-18 18:04               ` Knut Petersen
2012-07-18 19:34                 ` Adam Jackson
2012-07-19  6:04                   ` Knut Petersen
2012-07-20 12:03               ` Knut Petersen
2012-07-20 15:10                 ` Adam Jackson
2012-07-20 16:01                   ` Knut Petersen
2012-07-17 20:41   ` Knut Petersen

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=1342622195_12548@CP5-2952 \
    --to=chris@chris-wilson.co.uk \
    --cc=ajax@redhat.com \
    --cc=intel-gfx@lists.freedesktop.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