linux-kernel - Re: [PATCH v3] Input: Elan HID-I2C device driver

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] [day] [month] [year] [list]

Date:	Fri, 13 Apr 2012 18:21:53 +0200
From:	"Henrik Rydberg" <rydberg@...omail.se>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Benjamin Tissoires <benjamin.tissoires@...il.com>,
	林�┯� <tom_lin@....com.tw>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
	djkurtz@...omium.org
Subject: Re: [PATCH v3] Input: Elan HID-I2C device driver

On Fri, Apr 13, 2012 at 02:43:14PM +0200, Jiri Kosina wrote:
> On Thu, 12 Apr 2012, Benjamin Tissoires wrote:
> 
> > I read Microsoft's things about HID over I2C few days ago. And from
> > what I understood, the report descriptors and the enumeration of the
> > devices are stored in the ACPI table and not in the device itself. Can
> > you confirm this?
> > 
> > I was thinking about making hid-multitouch independent from the usb
> > stack and was thinking about doing the i2c-hid bridge. However, I did
> > not start writing a line yet ;-)
> 
> I guess you were planning to write that as a HID transport (ll) driver, 
> right?

Sounds great. The recent investigations into the properties of the hid
device identity for multitouch suggests that the ll driver could be
seen as the owner of the hid device itself, and should take on the
responsibility of both report fixups and determining the device
identify (read modalias). Using generic code (hid-owner?) of course. I
am experimenting with a couple of patches for it. Would you all agree
with this assessment?

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