[Intel-gfx] [Mesa3d-dev] mesa doesn't work with compiz (i965 + tips of all branches)
idr at freedesktop.org
Thu Jul 1 19:32:44 CEST 2010
-----BEGIN PGP SIGNED MESSAGE-----
Note: I'm sending this reply to mesa-dev at lists.freedesktop.org instead
of the old mailing list.
Maxim Levitsky wrote:
> On Tue, 2010-06-29 at 15:49 -0700, Ian Romanick wrote:
> Corbin Simpson wrote:
>>>> Curious. Admittedly I can't look at the content of that commit, but they
>>>> can't be too useless if compiz selects them. IIRC the point was to limit
>>>> the runtime of Intel internal tests; can't those tests be amended
>>>> instead? The number of configs will only grow; r300g has over 200 now
>>>> thanks to multisampling.
> The configs are useless. Applications can only ask for "bits >= X".
> There are still 24-bit depth / 8-bit stencil configs, and, last time I
> checked, 8 >= 0. There is no way to ask for a 24/0 config that wouldn't
> instead give a 24/8 config.
>>>> Posting from a mobile, pardon my terseness. ~ C.
>>>>> On Jun 29, 2010 1:28 PM, "Maxim Levitsky" <maximlevitsky at gmail.com
>>>>> <mailto:maximlevitsky at gmail.com>> wrote:
>>>>> On Tue, 2010-06-29 at 20:34 +0300, Maxim Levitsky wrote:
>>>>>> On Sun, 2010-06-27 at 19:07 +0300, Maxim ...
>>>>> Bisected this to
>>>>> 73e24cd5a7a0760726a681dda5b88805ddcf1555 is first bad commit
>>>>> commit 73e24cd5a7a0760726a681dda5b88805ddcf1555
>>>>> Author: Ian Romanick <ian.d.romanick at intel.com
>>>>> <mailto:ian.d.romanick at intel.com>>
>>>>> Date: Mon Feb 8 10:34:52 2010 -0800
>>>>> intel: Stop exposing useless 24 depth/0 stencil configs
> I need two pieces of information:
> - A diff of the output of glxinfo immediately before and immediately
> after this commit.
> - A list of what config attributes compiz is requesting. It should
> be easy enough to instrument choose_visual in glxcmds.c to dump out
> It should be pretty easy to root-cause this problem with that data.
> What is interesting is this:
> -0x62 32 tc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 0 0 None
Yup. That has to be it. The fix will have two parts. First, make the
3D driver a this specific visual. That will make "new" 3D drivers work
with "old" 2D drivers. Second, make the 2D driver mark this visual has
having stencil. The memory is there (interleaved with the 24-bits of
depth), so we may as well expose it.
If there's not a bugzilla for this, could you create one? This will
ensure that I get this fixed sooner rather than later. This also helps
us get it into a stable Mesa release.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the Intel-gfx