AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Kleiner <mario.kleiner.de-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>
Cc: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Depth 30 enablement for ati-ddx + exa. Rev 3
Date: Fri, 26 Jan 2018 22:42:44 +0100	[thread overview]
Message-ID: <3e8f6391-8e2f-591e-4341-ead830f72def@gmail.com> (raw)
In-Reply-To: <24d16c05-9d78-b5fd-4f0c-4e64577be1c4-otUistvHUpPR7s880joybQ@public.gmane.org>

On 01/25/2018 05:06 PM, Michel Dänzer wrote:
> On 2018-01-24 06:35 PM, Mario Kleiner wrote:
>> On 01/22/2018 07:01 PM, Michel Dänzer wrote:
>>> On 2018-01-22 03:14 AM, Mario Kleiner wrote:
...
>> Having the extension enabled in the ddx is needed for any test to work.
>> But when i set a breakpoint on EVERGREENDisplayTexturedVideo() in
>> evergreen_textured_videofuncs.c, that breakpoint is never hit, even in
>> depth 24 when XvMC tests work, so i'm not sure if i'm looking at mostly
>> unused code there?
> 
> I guess so. :)

Good, then i don't need to look at that code anymore :).

...
>>
>> It only happens if a client wants a fbconfig with alpha channel, for
>> destination alpha blending etc., as my application happens to. If you
>> only run glxgears or a desktop compositor like kde-5's, it won't happen
>> as they only use bgrx configs without alpha.
> 
> I sent out a patch which should fix this, please test.

Yes, that patch "[PATCH xf86-video-ati] Always use screen depth/bpp for 
KMS framebuffers" makes sense to me and fixes it nicely, as tested under 
dri3 and dri2 with glamor and exa:

Reviewed-and-Tested-by: Mario Kleiner <mario.kleiner.de@gmail.com>

I assume amdgpu-ddx will need the same treatment, as "Use reference 
counting for tracking KMS framebuffer lifetimes" which caused the 
problem has been ported to amdgpu-ddx.

-mario
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2018-01-26 21:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22  2:14 Depth 30 enablement for ati-ddx + exa. Rev 3 Mario Kleiner
     [not found] ` <20180122021437.9361-1-mario.kleiner.de-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-22  2:14   ` [PATCH 1/4] Define per x-screen individual drmmode_crtc_funcs Mario Kleiner
2018-01-22  2:14   ` [PATCH 2/4] Skip xf86HandleColormaps() at color depth 30. (v2) Mario Kleiner
2018-01-22  2:14   ` [PATCH 3/4] exa: Accelerate ARGB2101010 pictures Mario Kleiner
2018-01-22  2:14   ` [PATCH 4/4] Support exa screen color depth 30 on Linux 3.16 and later. (v2) Mario Kleiner
2018-01-22 18:01   ` Depth 30 enablement for ati-ddx + exa. Rev 3 Michel Dänzer
     [not found]     ` <04923fbb-dffb-b849-2f59-16e1f993a728-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-01-24 11:35       ` Michel Dänzer
2018-01-24 17:35       ` Mario Kleiner
     [not found]         ` <046a48e6-ef6d-11b4-99ec-8a8f668df5e6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-25 16:06           ` Michel Dänzer
     [not found]             ` <24d16c05-9d78-b5fd-4f0c-4e64577be1c4-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-01-26 21:42               ` Mario Kleiner [this message]
     [not found]                 ` <3e8f6391-8e2f-591e-4341-ead830f72def-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-29 11:50                   ` Michel Dänzer
2018-03-04  7:25       ` [ANNOUNCE] xf86-video-amdgpu 18.0.0 Mario Kleiner
     [not found]         ` <bca9b6ef-c675-95ba-fe02-4e5821902066-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-03-05  9:55           ` Michel Dänzer

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=3e8f6391-8e2f-591e-4341-ead830f72def@gmail.com \
    --to=mario.kleiner.de-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=michel-otUistvHUpPR7s880joybQ@public.gmane.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