On Sat, 20 Dec 2008 14:00:59 +0100 Arjen de Korte <[email protected]> wrote:
> Another useful thing would be to run the bundled driver on a Windows > box while running 'usbsnoop' so that we can get an idea what it is > doing. Maybe we're missing something here. Keep in mind that the patched megatec_usb driver (which I use since yesterday) can continiously read the status with no stability or timeout problems whatsoever, even though the data it receives is a bit corrupted. megatec_usb: (216.6 20010.0 1.0 22.0 50.1 13.8 25.0 00001001 blazer_usb: (206.0 206.4 206.4 023 50.1 13.8 25.0 00001001 So perhaps it's a matter of finding, which of the differences between those two drivers could cause both the difference in returned data, and blazer's hang after the successful first read. -- With respect, Roman _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
