Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Romanick <idr@freedesktop.org>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: "mesa-dev@lists.freedesktop.org" <mesa-dev@lists.freedesktop.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Mesa3d-dev] mesa doesn't work with compiz (i965 + tips of all branches)
Date: Thu, 01 Jul 2010 10:32:44 -0700	[thread overview]
Message-ID: <4C2CD13C.5050803@freedesktop.org> (raw)
In-Reply-To: <1277939603.4138.15.camel@localhost.localdomain>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Note: I'm sending this reply to mesa-dev@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@gmail.com
>>>>> <mailto:maximlevitsky@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@intel.com
>>>>> <mailto:ian.d.romanick@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
>     attribList.
> 
> It should be pretty easy to root-cause this problem with that data.

[snip]

> 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.

Thanks.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkws0TkACgkQX1gOwKyEAw8AiQCfeBiSF8kwHw5r93HREUpNdFu9
KOIAnRAY2rJUIvrrtYAZ/OAEI4GKmSqY
=bV5i
-----END PGP SIGNATURE-----

  reply	other threads:[~2010-07-01 17:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-27 16:07 mesa doesn't work with compiz (i965 + tips of all branches) Maxim Levitsky
2010-06-29 17:34 ` Maxim Levitsky
2010-06-29 20:27   ` [Mesa3d-dev] " Maxim Levitsky
2010-06-29 20:47     ` Corbin Simpson
2010-06-29 22:49       ` Ian Romanick
2010-06-30 23:13         ` Maxim Levitsky
2010-07-01 17:32           ` Ian Romanick [this message]
2010-07-03 23:32             ` Maxim Levitsky
2010-07-05  9:07             ` Michel Dänzer
2010-07-05 10:08               ` Maxim Levitsky
2010-07-05 15:22                 ` [Mesa-dev] " Maxim Levitsky
2010-07-05 15:57                   ` [Intel-gfx] " Kristian Høgsberg

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=4C2CD13C.5050803@freedesktop.org \
    --to=idr@freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maximlevitsky@gmail.com \
    --cc=mesa-dev@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