26.04.2020 19:12, Michał Mirosław пишет: > On Sun, Apr 26, 2020 at 06:41:34PM +0300, Dmitry Osipenko wrote: >> 26.04.2020 18:39, Dmitry Osipenko пишет: >>> 26.04.2020 14:21, Michał Mirosław пишет: >>>> On Sat, Apr 25, 2020 at 09:52:00PM -0700, Dmitry Torokhov wrote: >>>>> On Mon, Apr 13, 2020 at 03:32:23PM +0200, Michał Mirosław wrote: >>>>>> Driver only ever reports MT events. Clear capabilities of all others. >>>>> This is not true. input_mt_sync_frame() calls >>>>> input_mt_report_pointer_emulation() which does emut single-touch events >>>>> for the benefit of older userspace (or userspace that is not interested >>>>> in multitouch). >>>> >>>> Oh, I didn't notice that. Looking at the code, I see that >>>> input_mt_init_slots() sets up the emulated axes in this case. >>>> >>>> Do you need me to update the commitmsg? >>> >>> I tried Ubuntu 12.04 that uses ancient libinput (or whatever it was back >>> then), which doesn't support MT. Mouse doesn't move at all with this >>> patch being applied. Without this patch mouse moves, but it's not usable >>> because the cursor's position is wrong, i.e. mouse position doesn't >>> match the screen touches. >>> >>> This means that input_mt_report_pointer_emulation() doesn't set up >>> everything needed for the legacy pointer emulation. >>> >> >> I meant the input_mt_init_slots(). > > Can you try v4 and see if it helps? input_mt_init_slots() needs other > axes set up before for it to use correct ranges. Sure! I'll try it right now.
