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 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
