From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110659] pageflipping seems to cause jittering on mouse input when running Hitman 2 in Wine/DXVK with amdgpu.dc=1
Date: Wed, 04 Sep 2019 15:14:13 +0000 [thread overview]
Message-ID: <bug-110659-502-rDXkLsRQS0@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110659-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 816 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #66 from Michel Dänzer <michel@daenzer.net> ---
(In reply to tempel.julian from comment #65)
> Since this commit, the modesetting driver shows the same behavior as
> xf86-video-amdgpu:
> https://gitlab.freedesktop.org/xorg/xserver/commit/
> f0d78b47ac49977a6007f5fe081f00c6eb19a12e
Hmm, could the property update be part of the legacy => atomic compatibility
code in the kernel?
> So, now only xwayland isn't affected. But I think this can very well be just
> because Wayland compositors yet don't support turning compositing off in
> fullscreen.
They still use page flipping though, similar to TearFree. Which Wayland
compositor(s) have you tried?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1898 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-09-04 15:14 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-110659-502@http.bugs.freedesktop.org/>
2019-05-15 10:15 ` [Bug 110659] pageflipping seems to cause jittering on mouse input when running Hitman 2 in Wine/DXVK with amdgpu.dc=1 bugzilla-daemon
2019-05-15 12:17 ` bugzilla-daemon
2019-05-16 16:06 ` bugzilla-daemon
2019-05-24 19:34 ` bugzilla-daemon
2019-05-26 20:08 ` bugzilla-daemon
2019-05-27 13:05 ` bugzilla-daemon
2019-05-27 14:13 ` bugzilla-daemon
2019-05-27 14:22 ` bugzilla-daemon
2019-05-27 17:00 ` bugzilla-daemon
2019-05-27 17:11 ` bugzilla-daemon
2019-05-27 17:31 ` bugzilla-daemon
2019-05-27 17:53 ` bugzilla-daemon
2019-05-27 17:59 ` bugzilla-daemon
2019-05-27 18:07 ` bugzilla-daemon
2019-05-27 19:42 ` bugzilla-daemon
2019-05-29 17:05 ` bugzilla-daemon
2019-05-29 18:05 ` bugzilla-daemon
2019-05-29 20:56 ` bugzilla-daemon
2019-06-07 9:03 ` bugzilla-daemon
2019-06-08 17:50 ` bugzilla-daemon
2019-06-08 17:50 ` bugzilla-daemon
2019-06-20 10:40 ` bugzilla-daemon
2019-06-27 15:17 ` bugzilla-daemon
2019-07-10 9:42 ` bugzilla-daemon
2019-07-10 13:50 ` bugzilla-daemon
2019-07-10 19:08 ` bugzilla-daemon
2019-07-18 21:30 ` bugzilla-daemon
2019-08-10 10:56 ` bugzilla-daemon
2019-08-21 17:49 ` bugzilla-daemon
2019-08-21 18:37 ` bugzilla-daemon
2019-08-21 18:40 ` bugzilla-daemon
2019-08-21 18:48 ` bugzilla-daemon
2019-08-21 18:53 ` bugzilla-daemon
2019-08-21 19:17 ` bugzilla-daemon
2019-08-21 19:18 ` bugzilla-daemon
2019-08-21 19:58 ` bugzilla-daemon
2019-08-21 20:26 ` bugzilla-daemon
2019-08-22 14:44 ` bugzilla-daemon
2019-08-22 16:21 ` bugzilla-daemon
2019-08-22 16:40 ` bugzilla-daemon
2019-08-22 17:00 ` bugzilla-daemon
2019-08-22 17:09 ` bugzilla-daemon
2019-08-22 18:14 ` bugzilla-daemon
2019-08-22 18:15 ` bugzilla-daemon
2019-08-25 15:44 ` bugzilla-daemon
2019-08-25 15:48 ` bugzilla-daemon
2019-08-26 12:39 ` bugzilla-daemon
2019-08-26 16:26 ` bugzilla-daemon
2019-08-29 12:54 ` bugzilla-daemon
2019-08-29 13:03 ` bugzilla-daemon
2019-08-29 13:23 ` bugzilla-daemon
2019-08-29 13:26 ` bugzilla-daemon
2019-08-29 13:35 ` bugzilla-daemon
2019-08-29 13:36 ` bugzilla-daemon
2019-08-29 13:43 ` bugzilla-daemon
2019-08-29 14:06 ` bugzilla-daemon
2019-08-29 14:07 ` bugzilla-daemon
2019-08-31 10:28 ` bugzilla-daemon
2019-08-31 10:29 ` bugzilla-daemon
2019-09-01 12:23 ` bugzilla-daemon
2019-09-02 13:41 ` bugzilla-daemon
2019-09-03 16:15 ` bugzilla-daemon
2019-09-03 20:43 ` bugzilla-daemon
2019-09-04 9:28 ` bugzilla-daemon
2019-09-04 15:14 ` bugzilla-daemon [this message]
2019-09-04 20:34 ` bugzilla-daemon
2019-09-06 12:08 ` bugzilla-daemon
2019-09-06 12:08 ` bugzilla-daemon
2019-09-06 13:53 ` bugzilla-daemon
2019-09-06 15:02 ` bugzilla-daemon
2019-09-06 15:02 ` bugzilla-daemon
2019-09-06 16:41 ` bugzilla-daemon
2019-09-06 16:45 ` bugzilla-daemon
2019-09-06 17:38 ` bugzilla-daemon
2019-09-09 14:06 ` bugzilla-daemon
2019-09-09 15:12 ` bugzilla-daemon
2019-09-09 15:29 ` bugzilla-daemon
2019-09-09 15:44 ` bugzilla-daemon
2019-09-09 17:53 ` bugzilla-daemon
2019-09-17 15:06 ` bugzilla-daemon
2019-09-17 17:20 ` bugzilla-daemon
2019-09-17 20:58 ` bugzilla-daemon
2019-09-18 16:55 ` bugzilla-daemon
2019-09-18 17:54 ` bugzilla-daemon
2019-09-18 19:10 ` bugzilla-daemon
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=bug-110659-502-rDXkLsRQS0@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.