Jiri Kosina wrote: > 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). > > After hearing your words, I change my implementation use hidraw as an event filter, IOW, the HID core will handle these events which hidraw can or need not handle. The modification is easy.
> BTW as soon as you have some presentable code, could you please send it so > that we could see what aproach you have taken? Debating over code is > usualy more efficient than just ranting random ideas :) > > Thanks, > > Of course, It's no problem. but it must be tomorrow, two reasons: 1. The development PC is at my home, I am not SOHO. 2. After change from "flip-flopping", the patch need some cleaning. Good luck. - Li Yu ------------------------------------------------------------------------- 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
