From: Carl Worth Subject: Re: [ANNOUNCE] xf86-video-intel 2.11.901 Date: Thu, 24 Jun 2010 23:23:11 -0700 Message-ID: <87fx0bfx68.fsf@yoom.home.cworth.org> References: <87typ5qgbp.fsf@yoom.home.cworth.org> <201006151605.15891.damnshock@gmail.com> <87ljaggs3u.fsf@yoom.home.cworth.org> <871vc4na83.fsf@yoom.home.cworth.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0440413193==" Return-path: Received: from olra.theworths.org (u15218177.onlinehome-server.com [74.208.220.233]) by gabe.freedesktop.org (Postfix) with ESMTP id C865A9E769 for ; Thu, 24 Jun 2010 23:23:22 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 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: Elias Gabriel Amaral da Silva Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org --===============0440413193== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" --=-=-= Content-Transfer-Encoding: quoted-printable On Mon, 21 Jun 2010 02:31:31 -0300, Elias Gabriel Amaral da Silva wrote: > When using an 2.9 driver compiled for 1.7 xorg, and 1.8 xorg, X > complains about ABI mismatch. Recompiling the driver is supposed to > fix this, but, I get the same error I got while building from git > sources. In fact I see it was already reported at gentoo bugzilla, > http://bugs.gentoo.org/317585 >=20 > Well, I suppose I could just downgrade X.. >=20 > Is 2.11 and beyond expected to work with Xorg 1.7? [ hmm, every time I > do this, I have to wait a while.. I'm using debian testing right now > (Xorg 1.7.5, intel driver 2.9.1) and it's working fine. ] Sorry about all this. There's a tight ABI binding between the X server and the xf86-video-intel driver. That means you can't compile the 2.9 driver with the latest X server, nor can you compile the latest driver with the X server that works with the 2.9 driver. That means it's impossible to hold one of these projects constant while bisecting the other, (or even just trying a couple of versions of the other to pinpoint it as the problematic component). That's unfortunate since bisecting would be extremely useful here. For this specific instance, one might be able to construct a patch to the 2.9 driver to make it compile against the latest X server. And then one could carry that patch along while bisecting. That will be a bit of work though. In the future, I think the right thing to do is to put the driver back into the X server repository. That would eliminate this problem entirely, (for future versions), and bisecting either X server or driver problems would work just fine. =2DCarl =2D-=20 carl.d.worth@intel.com --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFMJEtP6JDdNq8qSWgRAnZ0AJ96IYca6RR8fRconZapUsPQPFI1twCfXWyY Vlc0qIq213+oX2VdVzwjm4g= =qiGh -----END PGP SIGNATURE----- --=-=-=-- --===============0440413193== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx --===============0440413193==--