Displaying 2 results from an estimated 2 matches for "hidpaths".
2007 Aug 02
1
NUT and libhid
was: Re: [Nut-upsdev] usbhid-ups.h: hid_info_t structure
On 8/2/07, Peter Selinger <selinger at mathstat.dal.ca> wrote:
> All this needs to be replaced by a re-designed, cleaned-up data
> structure. It's on my to-do list, but nothing on that list will get
> done by me anytime soon. As nothing is technically broken, and the
> changes are prone to introducing subtle bugs, this
2007 Aug 23
1
[nut-commits] svn commit r1073 - in trunk: . drivers
I think having this logic buried within libhid/libusb
(libusb:libusb_open(), line 179 to 206) is ultimately a mistake,
albeit one that I am probably responsible for. Would it make sense to
confine libhid to low-level operations, and leave the decision of
trying to reopen vs. retrying to open to the high-level driver, in
this case usbhid-ups?
I envision that the code in usbhid-ups:reconnect_ups()