[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <721b91b0-f231-5f7d-a438-09dd85f63513@canonical.com>
Date: Sat, 25 May 2019 09:33:46 +0800
From: Hui Wang <hui.wang@...onical.com>
To: Peter Hutterer <peter.hutterer@...-t.net>
Cc: Pali Rohár <pali.rohar@...il.com>,
Xiaoxiao Liu <xiaoxiao.liu-1@...alps.com>,
dmitry.torokhov@...il.com, XiaoXiao Liu <sliuuxiaonxiao@...il.com>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Xiaojian Cao <xiaojian.cao@...alps.com>,
"zhangfp1@...ovo.com" <zhangfp1@...ovo.com>
Subject: Re: 答复: 答复: 答复: [PATCH] input: alps-fix the issue the special alps trackpoint do not work.
On 2019/5/24 下午6:58, Peter Hutterer wrote:
> On Fri, May 24, 2019 at 06:43:58PM +0800, Hui Wang wrote:
>> On 2019/5/24 下午5:37, Peter Hutterer wrote:
>>> On Fri, May 24, 2019 at 03:37:57PM +0800, Hui Wang wrote:
>>>>
>> OK, that is sth we need to do. But anyway it is a bit risky to backport
>> that much code and the whole folder of quirks to libinput 1.10.4, we need
>> to do lots of test to make sure there is no regression on other machines.
>>
>> Probably we only need to keep the quirks/30-vendor-alps.quirks to 1.10.4 and
>> drop other quirks, that will be better for our testing effort.
> might be worth looking at what is in 1.10.7, e.g. a3b3e85c0e looks like it
> may be of interest. That one suggests the range on some ALPS devices is over
> 100, so testing with 5-25 may really not have had any effect.
Oh, looks exactly the same as our issue, will have a try with it.
Thanks,
Hui.
>
> Cheers,
> Peter
>
Powered by blists - more mailing lists