On Sep 25, 2015, at 7:34 AM, Louis G. <lo...@frentzgzesh.info> wrote: >> One thing I noticed about the report descriptor that NUT returned: it has >> extra zero bytes. >> >> For instance, these lines: >> >> 0.157417 Report Descriptor: (656 bytes) => 05 00 84 00 09 00 04 00 a1 00 01 >> 00 09 00 >> 0.157431 24 00 a1 00 00 00 85 00 01 00 09 00 fe 00 75 00 08 00 95 00 01 00 >> 15 00 00 >> >> would parse fairly normally if they read as follows: >> >> 0.157417 Report Descriptor: (656 bytes) => 05 84 09 04 a1 01 09 >> 0.157431 24 a1 00 85 01 09 fe 75 08 95 01 15 00 > > Here is the output from that command. Thank you for your help. > > usbconfig -u 4 -a 2 do_request 0x81 0x06 0x2200 0 0x100 > REQUEST = <0x05 0x84 0x09 0x04 0xa1 0x01 0x09 0x24 0xa1 0x00 0x85 0x01 0x09 > 0xfe 0x75 0x08 0x95 0x01 0x15 0x00 [...]
Yeah, for some reason, NUT is getting different descriptor data than usbconfig. I don't see anything obvious in the FreeBSD source code, and I can't test the latest FreeBSD on my systems here (computers are in pieces in the basement). Is there a chance that there is something different with NAS4Free's USB stack? Where do they keep their source code repository? Or can you test NUT with actual FreeBSD 10.2 system? -- Charles Lepple clepple@gmail _______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser