On Apr 5, 2013, at 3:04 AM, Matus UHLAR - fantomas wrote:
libusb: 0.000000 error [get_config_descriptor] short output read 0/8
On 05.04.13 20:39, Charles Lepple wrote:
Reading the config descriptor is a pretty basic operation. What does "lsusb
-vvv -d 0463:ffff" return?
On Apr 6, 2013, at 10:08 AM, Matus UHLAR - fantomas wrote:
too much of output to send here:
http://test.fantomas.sk/tplink2543nd_lsusb-vvv-d_0463:ffff
On 06.04.13 10:20, Charles Lepple wrote:
Hmm, perhaps Arnaud can ask someone what the other five configurations are:
idVendor 0x0463 MGE UPS Systems
idProduct 0xffff UPS
bcdDevice 1.00
iManufacturer 1 EATON
iProduct 2 Protection Station
iSerial 4 AN2E49008
bNumConfigurations 6
Is there any way you can build against the real libusb-0.1, versus the
compatibility layer from 1.0? They may have different error checking
strategies when reading descriptors.
I don't think I can build it anywhere now (no experience with
cross-compiling on different architecture), but I can try looking at it on
my QNAP NAS and linux PC.
...it seems that openwrt uses libusbx fork, version 1.0.9 and there's 1.0.12
available with some changes to related code...
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
On the other hand, you have different fingers.
_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
