[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 04 Apr 2007 16:54:49 +0200
From: Marcel Holtmann <marcel@...tmann.org>
To: Jiri Kosina <jkosina@...e.cz>
Cc: Li Yu <raise.sail@...il.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
yanghong@...ss.com.cn,
linux-usb-devel <linux-usb-devel@...ts.sourceforge.net>,
hongzhiyi@...ss.com.cn, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [linux-usb-devel] [RFC] HID bus design overview.
Hi Jiri,
> > What's the position of hidraw? It only is used when all other driver is
> > not usable on some report? or, it should be stick every working device.
>
> Current implementation (as you can see it in -mm or in my hid.git tree) is
> creating hidraw interface for just every HID device/interface. But this
> will get changed before merge.
>
> Passing just everything to hidraw is not a good option, as this could lead
> to confusion and duplicating of input events (i.e. in-kernel hid driver
> processes the report and generates input_event(), and also userland driver
> obtains data from hidraw and generates input event through uinput ... not
> good).
at some point I thought it would be nice to have something like hiddump
(like tcpdump), but that can be easily achieved with hcidump and usbmon
on the lower level.
So if hidraw claims a report id, the kernel should no longer handle it.
Regards
Marcel
-
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