linux-kernel - Re: [PATCH 0/2] autodetection of multitouch devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 28 Sep 2011 23:25:38 +0200
From:	Benjamin Tissoires <benjamin.tissoires@...c.fr>
To:	Stéphane Chatty <chatty@...c.fr>
Cc:	Jiri Kosina <jkosina@...e.cz>,
	Henrik Rydberg <rydberg@...omail.se>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	USB list <linux-input@...r.kernel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] autodetection of multitouch devices

On Wed, Sep 28, 2011 at 22:32, Stéphane Chatty <chatty@...c.fr> wrote:
>
> Le 26 sept. 2011 à 16:47, Jiri Kosina a écrit :
>
>> On Mon, 26 Sep 2011, Henrik Rydberg wrote:
>>
>>>>> These two patches finally enable the kernel to handle multitouch devices correctly.
>>>>> If a device presents in its report descriptors the usage Contact ID, then it is considered as
>>>>> a multitouch device and handled by hid-multitouch.
>>>>
>>>> Hi Banjamin,
>>>>
>>>> thanks a lot for working on this. I have now queued the patches in my
>>>> tree.
>>>
>>> Hi Benjamin,
>>>
>>> Late as it seems, here are a couple of questions:
>>>
>>> 1. How was this tested? By removing all white-listed devices in
>>> hid-multitouch.c to see if the usual suspects are still picked up?

Well, nearly all the devices that has been included since March passed
the first patch (I had it in my queue since a long time).
For now, only Stantum products are known to not work with this patch
if we remove them from hid_have_special_driver.

As for the blacklist problem, we also know that this is not very
beautiful, but we are working on a better solution. For the moment, it
just allows people to have their device working out of the box
(crossing fingers).

Cheers,
Benjamin


>>
>> If we didn't have full test coverage (which I suppose to be the case), we
>> can still revert to the old method after the merge window if there reports
>> that this broke things on particular devices.
>>
>> Do you guys at least have report descriptor dumps from most of the
>> supported devices?
>
>
> Yes, we have report descriptors for about 20-30 different models now, and about 10 actual devices for testing purposes. Unfortunately, this still does not tell us exactly how all these devices manage to work with the same Win 7 driver, given their diversity. We are getting close, but just not yet.
>
> BTW we gladly accept to receive sample panels from vendors, this usually ensures fast support. Additionally, the panels are then reused by ENAC students in their projects, so this stimulates the market of multitouch devices in aviation :-)
>
> Cheers,
>
> St.
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/