dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: sylvain.bertrand@gmail.com
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [amdgpu][tahiti xt] cursor motion smoothness
Date: Tue, 3 Jul 2018 11:01:46 +0200	[thread overview]
Message-ID: <67a86569-1be3-e6a8-2c9c-e1f84b4e06db@daenzer.net> (raw)
In-Reply-To: <e5de99df-48ac-730f-0ab9-7ba2ca42664e@daenzer.net>

On 2018-07-03 10:54 AM, Michel Dänzer wrote:
> On 2018-07-02 10:10 PM, sylvain.bertrand@gmail.com wrote:
>> On Mon, Jul 02, 2018 at 06:43:48PM +0200, Michel Dänzer wrote:
>>>> Sending the logs as direct email to your personal email box.
>>>
>>> Does using xf86-input-libinput instead of xf86-input-evdev help?
>>
>> I did plan to switch to libinput in the futur, but:
>>
>> I did test the xinput events and I get for a reasonable mouse motion speed an
>> update of coords for each column of the screen (full hd).
>>
>> It means that the cursor is supposely displayed for nearly all columns of the
>> screen. For a fast mouse motion, the coord updates jump to a few tens of
>> pixels.  (1000Hz mouse)
>>
>> Those numbers does not change from 60Hz to 144Hz, then I can rule out the input
>> code.
>>
>> If it's not my eyes or the screen itself, the pb will be in the cursor update
>> code path from the xserver down to the driver...
> 
> Unless your xserver build ends up with INPUTTHREAD undefined for some
> reason, input events are processed in a separate thread, and the HW
> cursor position is updated accordingly ASAP.

Also make sure you do not pass -dumbSched on the Xorg command line, and
do not disable Option "SilkenMouse" in xorg.conf.


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-07-03  9:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-01 12:52 [amdgpu][tahiti xt] cursor motion smoothness sylvain.bertrand
2018-07-02  9:24 ` Michel Dänzer
2018-07-02  9:29   ` Michel Dänzer
2018-07-02 14:04     ` sylvain.bertrand
2018-07-02 14:22       ` Michel Dänzer
2018-07-02 15:28         ` sylvain.bertrand
2018-07-02 16:43           ` Michel Dänzer
2018-07-02 20:10             ` sylvain.bertrand
2018-07-03  8:54               ` Michel Dänzer
2018-07-03  9:01                 ` Michel Dänzer [this message]
2018-07-03 14:46                   ` sylvain.bertrand
2018-07-03 17:06                     ` Michel Dänzer
2018-07-03 14:40                 ` sylvain.bertrand
2018-07-02 16:30         ` sylvain.bertrand

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=67a86569-1be3-e6a8-2c9c-e1f84b4e06db@daenzer.net \
    --to=michel@daenzer.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=sylvain.bertrand@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).