From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: [BUG] intel_drv.so fails to load Date: Wed, 18 Jul 2012 23:34:12 +0100 Message-ID: <1342650875_13958@CP5-2952> References: <5005C642.6030102@t-online.de> <1342556238_9775@CP5-2952> <1342557713_9832@CP5-2952> <5005D10E.4080101@t-online.de> <1342559830_9900@CP5-2952> <1342620128.3590.13.camel@atropine> <1342620454_12433@CP5-2952> <1342621766.3590.29.camel@atropine> <1342622195_12548@CP5-2952> <1342640864.3590.71.camel@atropine> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from fireflyinternet.com (smtp.fireflyinternet.com [109.228.6.236]) by gabe.freedesktop.org (Postfix) with ESMTP id 7E3A09E7CC for ; Wed, 18 Jul 2012 15:34:41 -0700 (PDT) In-Reply-To: <1342640864.3590.71.camel@atropine> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Adam Jackson Cc: intel-gfx List-Id: intel-gfx@lists.freedesktop.org On Wed, 18 Jul 2012 15:47:44 -0400, Adam Jackson wrote: > So we default to asking for XAA, and if it doesn't load (because you > built without it) then neither will the driver; conversely, if XAA > loads, DRI's use of XAA symbols would be safe. You'd have to have asked > for Option "NoAccel" to hit that bug. I had not noticed that the code still implied a dependence upon the XAA module. > It's not clear to me if, subsequent to your change, DRI would work with > NoAccel. It does. The mapping of the ring and control registers was already managed outside of the XAA specific routines, so enabling the blit function without the XAA infrastructure is fine. Tested insofar as running glxgears on a remote i815 with XAA exorcised. Not totally convinced I've verified all the necessary paths, but it loads and seems to run. -Chris -- Chris Wilson, Intel Open Source Technology Centre