Hi Linus, > > Here are some patches that move the HID code to a new directory allowing > > it to be used by other kernel subsystems easier. > > I pulled. However, I think the Kconfig changes are HORRIBLE. > > I don't understand why people don't use "select" more. Why should Kconfig > ask for "Generic HID support?" That question _never_ makes sense to a > user. And if you answer "n", you'll not get USB_HID. > > This is not user-friendly. If you need HID support, just select it. Don't > ask people questions that make no sense. If the generic HID code is needed > for some driver, you just select it. If it's not needed, you don't. It's > that easy.
since we don't have any user-space or out of kernel HID transport drivers at the moment it would make sense to simply select HID if someone selects USB_HID or the upcoming Bluetooth transport. 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 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
