On 2018-07-03 10:54 AM, Michel Dänzer wrote: > On 2018-07-02 10:10 PM, sylvain.bertrand@xxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
