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: [ANNOUNCE] xf86-video-amdgpu 18.0.0
Date: Sun, 4 Mar 2018 08:25:03 +0100 [thread overview]
Message-ID: <bca9b6ef-c675-95ba-fe02-4e5821902066@gmail.com> (raw)
In-Reply-To: <04923fbb-dffb-b849-2f59-16e1f993a728-otUistvHUpPR7s880joybQ@public.gmane.org>
Hi Michel,
wrt. our conversation from ~ 1 month ago:
On 01/22/2018 07:01 PM, Michel Dänzer wrote:
> On 2018-01-22 03:14 AM, Mario Kleiner wrote:
>
>> When testing against current master in dual-x-screen mode,
>> i found out that the current ati-ddx commit at the top 1fe8ca75974c52
>> "Keep track of how many SW cursors are visible on each screen"
>> breaks multi x-screen setups by screwing up cursor handling.
>
> I stumbled over this myself the other day. There's an issue with the
> (un)wrapping of miPointerSpriteFuncRec entries. Not sure yet what
> exactly's wrong with it though. I'll look into it.
>
Has the multi-x-screen breakage been fixed for amdgpu 18.0.0? I can't
see a commit hinting at a fix, and i assume it was broken by the new HW
cursor + pageflip logic, just as in the xf86-video-ati case? I can't
test anything myself atm. as my only amdgpu capable gpu has left me :(
Broken multi-x-screen from an official driver release ending in a distro
would be a big problem for many vision scientists, as they depend on AMD
+ dual-x-screen support for their work.
Thanks,
-mario
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2018-03-04 7:25 UTC|newest]
Thread overview: 14+ 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
[not found] ` <3e8f6391-8e2f-591e-4341-ead830f72def-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-29 11:50 ` Michel Dänzer
2018-03-04 7:25 ` Mario Kleiner [this message]
[not found] ` <bca9b6ef-c675-95ba-fe02-4e5821902066-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-03-05 9:55 ` [ANNOUNCE] xf86-video-amdgpu 18.0.0 Michel Dänzer
-- strict thread matches above, loose matches on Subject: below --
2018-03-02 17:44 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=bca9b6ef-c675-95ba-fe02-4e5821902066@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