linux-kernel - Re: [PATCH 2/2] input: Add a detailed multi-touch finger data report protocol (rev2)

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:	Tue, 6 Jan 2009 23:50:57 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Jim Gettys <jg@...top.org>
cc:	Henrik Rydberg <rydberg@...omail.se>, Greg KH <greg@...ah.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-input@...r.kernel.org,
	Peter Hutterer <peter.hutterer@...-t.net>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] input: Add a detailed multi-touch finger data	report
 protocol (rev2)

On Tue, 6 Jan 2009, Jim Gettys wrote:

> 1) Does anyone know if Microsoft has actually made the proposal to the
> USB IF?  Is there anyone in the community watching/commenting on USB IF
> proposals?

This would be question for Greg.

> 2) do you want generic USB HID patches or do you want to, for now, 
> confine these to USB device specific drivers as much as possible?

We already have a lot of drivers for special HID devices that emit usages 
that have not been defined by HID standard. These drivers are independent 
on the underlying transport (USB, Bluetooth). Therefore all you ideally 
need to do is to add just another driver which hooks itself to HID bus and 
performs all that is needed in addition to what generic HID code does. 
There are lot of such drivers in drivers/hid/hid-*.c which you can use as 
examples. Please let me know if you have any further questions.

-- 
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/