2009/9/3 Charles Lepple <[email protected]> > On Sep 3, 2009, at 9:22 AM, Arnaud Quette wrote: > > The codeless kext stuff is not too complicated - we could probably >> generate them the same way as the udev configuration files. The only >> trick is that the USB VID, PID, bConfigurationValue, bInterfaceNumber >> and bcdDevice values need to be included, in decimal (and the latter >> probably needs to be extracted from lsusb output that users have >> posted to the mailing lists). >> >> isn't there some joker for the b* (like "*" meaning any value)? >> > > I'll have to check, but see below. > > having the option to match so specifically is nice, but I find strange to >> be forced to do that! >> > > The problem is that you have to be more specific than the general HID class > drivers. There is a "matching score" that the codeless kext has to beat in > order to allow libusb to claim the device/interface. Wildcards do not > increase the score as much as specific values. >
yup, but do you think there will be other higher values (ie that matches better than nut)? > Now, if we were using a cross-platform HID library... but I digress :-) > ;-) cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/
_______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
