On Friday 24 May 2019 19:32:38 Peter Hutterer wrote: > On Fri, May 24, 2019 at 09:26:48AM +0200, Pali Rohár wrote: > > On Friday 24 May 2019 13:50:53 Hui Wang wrote: > > > On 2019/5/24 下午1:36, Peter Hutterer wrote: > > > > On Fri, May 24, 2019 at 01:25:52PM +0800, Hui Wang wrote: > > > > > On 2019/5/23 下午2:01, Peter Hutterer wrote: > > > > > > On Wed, May 22, 2019 at 09:40:30AM +0200, Pali Rohár wrote: > > > > > > > On Wednesday 22 May 2019 07:30:43 Xiaoxiao Liu wrote: > > > > > > > > Hi Pali, > > > > > > > > > > > > > > > > Ok, and cannot you set ALPS_DUALPOINT flag based on that > > > > > > > > alps_check_is_trackpoint() result and then update > > > > > > > > alps_process_packet_ss4_v3() code to supports also > > > > > > > > V8 trackpoint packets? > > > > > > > > --> Yes, we can do like so, when we use the v8 method to process the trackpoint , the mouse speed is not ideal. > > > > > > > > Then we choose the standard mouse driver. > > > > > > > Mouse speed is something which is configurable. Have you configured it > > > > > > > somehow? Also there is libinput project should handle these settings > > > > > > > more properly. > > > > > > > > > > > > > > Adding Peter Hutterer, maintainer of libinput to loop. I think he could > > > > > > > help with this problem. > > > > > > libinput has a quirk for a magic multiplier on trackpoints. it was the only > > > > > > solution I found that came close to "working" given that every device seems > > > > > > to provide some other random magic data. Doc for it is here: > > > > > > https://wayland.freedesktop.org/libinput/doc/latest/trackpoint-configuration.html > > > > > Hello Peter Hutterer, > > > > > > > > > > To adjust the trackpoint speed from userspace: > > > > > > > > > > If the libinput version is lower than 1.9.0, we could set > > > > > POINTINGSTICK_CONST_ACCEL=0.25 > > > > > > > > > > If the libinput version is higher than 1.12.0, we could set > > > > > AttrTrackpointMultiplier=0.25 > > > > > > > > > > But if we use libinput-1.10.0, how could we adjust the speed? > > > > The LIBINPUT_ATTR_TRACKPOINT_RANGE property, which didn't end up working > > > > well (hence why it got replaced again). See the docs here though: > > > > https://wayland.freedesktop.org/libinput/doc/1.10.0/trackpoints.html > > > > > > > > Cheers, > > > > Peter > > > > > > OK, got it, Thanks. > > > > Is not here some database where for input device name / id is specified > > that property? So users do not have to invent what is correct value for > > their hardware? > > yeah, libinput ships with a quirks database that sets those, but it relies > on users to submit the quirks. > https://gitlab.freedesktop.org/libinput/libinput/tree/master/quirks That is enough! > There's no "correct" value anyway, if you ask 3 users what the trackpoint > should do you'll get 5 answers :) I know :) but reason for such database is to provide some sane defaults. Which seems it is already there. -- Pali Rohár pali.rohar@xxxxxxxxx
