[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0703052244490.10909@twin.jikos.cz>
Date: Mon, 5 Mar 2007 22:47:10 +0100 (CET)
From: Jiri Kosina <jikos@...os.cz>
To: Marcel Holtmann <marcel@...tmann.org>
cc: Li Yu <raise.sail@...il.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Greg Kroah Hartman <greg@...ah.com>,
linux-usb-devel <linux-usb-devel@...ts.sourceforge.net>,
LKML <linux-kernel@...r.kernel.org>,
Vincent Legoll <vincentlegoll@...il.com>,
"Zephaniah E. Hull" <warp@...allh.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Harold Sargeant <harold-sargeant@...world.com>,
liyu <liyu@...ss.com.cn>
Subject: Re: [DOC] The documentation for HID Simple Driver Interface 0.5.0
On Mon, 5 Mar 2007, Marcel Holtmann wrote:
> actually, I don't think we need a simple driver interface. We need a HID
> driver interface in general. For example that you can register a driver
> for one or multiple report ID and then it handles input and output for
> these report IDs. This also means that the current keyboard and mouse
> input devices will become a HID driver.
Hi Marcel,
sorry, this is not clear to me - what keyboard and mouse devices are you
talking here precisely? As not all keyboard and mouse devices are HID,
this is probably not what you've meant ... ? Thanks.
> In addition to the kernel HID driver we might also when have a new
> hidraw (or modified hiddev) interface that allows to handle specific
> report ID from a userspace application. Especially when it comes to LED
> displays or UPS systems.
I have already written some code of hidraw interface, but it's not yet
finished due to too many other pending things.
Thanks,
--
Jiri Kosina
-
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