On Mon, 1 Jun 2009, Arjen de Korte wrote: > Citeren Daniel O'Connor <[email protected]>: > > OK, so it needs another entry for this particular UPS? I wonder if > > there is some more general way of detecting this particular > > implementation.. > > No. The problem here is that APC uses the same HID path in different > ways. Since they also use a single VID:PID combination for all their > devices, there is no easy way to tell when to use date_conversion() > and when to use apc_date_conversion().
OK. > It is tempting to base this on the size of the field that is > reported, but it would require a major amount of work on the base > usbhid-ups driver, since we only pass the parameters by value and not > by the full HID path information. Not that it isn't doable, but it > takes much more work than I'm prepared to spend on a vendor that > isn't really supportive with NUT. Fair enough. > Basically, I'm telling you that we probably won't fix this in the > near future. Yep, well NUT works perfectly well for what I want it for (better than expected given the vagaries of the USB stack on FreeBSD 6.x :) Thanks for your reply! -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
