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]
Message-ID: <alpine.LNX.2.00.1109261644250.24692@pobox.suse.cz>
Date:	Mon, 26 Sep 2011 16:47:00 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Henrik Rydberg <rydberg@...omail.se>
Cc:	Benjamin Tissoires <benjamin.tissoires@...il.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Benjamin Tissoires <benjamin.tissoires@...c.fr>,
	Stephane Chatty <chatty@...-enac.fr>,
	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] autodetection of multitouch devices

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?

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?

Thanks,

-- 
Jiri Kosina
SUSE Labs
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ