[Nut-upsdev] Tripplite USB 3003 problems
clepple at gmail.com
Wed Mar 31 01:43:42 UTC 2010
On Tue, Mar 30, 2010 at 4:36 PM, Wallis, Chase Civ USAF AFMC 519
SMXS/MXDEA <Chase.Wallis at hill.af.mil> wrote:
usb_interrupt_read() is in libusb (unlike the mis-named
libusb_get_interrupt()... argh...) so I don't really know what we're
doing wrong. Anything above that point is OS-specific.
>> More info and log messages can be found here:
>> if you are interested in any info, let me know and I'll ask the
> It may be similar/same. I think it may be too early to tell. Thoughts?
Probably too early to tell, but my hunch is that it is similar. NUT
usually can't cause the kernel to go haywire by itself - the drivers
usually have a reasonable polling speed, and the kernel should take
care of any timeouts or unexpected responses from the hardware.
- Charles Lepple
More information about the Nut-upsdev