On Wed, Nov 14, 2012 at 9:37 PM, Stuart Henderson <s...@spacehopper.org> wrote: > On 2012-11-14, Tomas Bodzar <tomas.bod...@gmail.com> wrote: >> However I think you need to do this (you need to do that and test on >> current anyway) >> http://undeadly.org/cgi?action=article&sid=20080315134047 or >> http://undeadly.org/cgi?action=article&sid=20070207152423 because I >> can't see your device in /usr/src/sys/dev/usb/usbdevs* > > For many USB devices, there are common device classes with > standard(ish) drivers, devices in those classes will automatically > attach to the relevant driver. In this case the device already > attaches to uhid(4) and ukbd(4) based on the device class. >
Maybe this can be problem http://deskthority.net/wiki/Noppoo_Choc_Mini here? Specifically http://deskthority.net/wiki/NKRO-over-USB_issues > >> On Wed, Nov 14, 2012 at 3:24 PM, yunplusplus <yunplusp...@163.com> wrote: >>> After the Noppoo keyboard plugged in, usbdevs -dv shows: > > This gives more information which might be useful, > > pkg_add usbutils > lsusb -d 1006: -v > > (-d 1006: restricts to devices matching the vendor ID of this keyboard).
