In message <[EMAIL PROTECTED]> you write:
>Vojtech Pavlik wrote:
><snip>
>> The patch is now added to the input CVS. I've done a deeper cut when
>> integrating it - I've split the original hid into the hid core and
>> hid-input bindings. Check the cvs (linuxconsole.sourceforge.net) for any
>> mistakes I did in the integration. It'll need some more work anyways.
>
>Any reason why this is linux/drivers/input rather than linux/drivers/usb?
>hiddev is more of an alternative to using HID events to feed higher level
>input layers. Crappy hand done ASCII art follows (I know that there are other
>elements now, or will be when I get the hiddev patches into my tree)
I'd tend to agree with this comment. My choice to use a USB minor number may be a
source of controversy in itself, but I think that hiddev is HID specific (I'd say it's
USB specific, except then I'd get someone chiming in and saying "don't forget IEEE
1394 HID."). The interfaces available through input subsystem, as I understand it,
are supposed to be independent of the way the devices are attached. I worked to make
the hiddev code architecturally independent of the input code as a result. Does this
way of thinking conflict with yours, Vojtech?
--
Paul
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
