On Dec 26, 2013, at 9:40 PM, Ariel Wainer wrote:>> It might be possible to tell usbhid-ups to match on the 0xFFA0 usage page, and ignore all of the other HID PDC definitions. I'll poke around the code. > > Ok, let me know if you need anything else. I tryed the instructions at > http://www.networkupstools.org/docs/developer-guide.chunked/ar01s04.html > , but it didn't work. As a matter of fact, the generated C files did not > compile, they had garbage in the middle. Hand editing the sources to > make it compile resulted in a non-working driver anyway, probably > because of the not implemented usages.Could you please send the debug output? (if it is more than ~ 30KB gzipped, just send it directly to me.) I was going to use the debug output from the earlier thread to generate those C files, but yeah, there are some additional bits needed. If nothing else, it would be good to improve the diagnostics for that script.> Happy $HOLYDAY ;)Thanks, same to you! -- Charles Lepple clepple at gmail
On 27/12/13 00:06, Charles Lepple wrote:> Could you please send the debug output? (if it is more than ~ 30KB > gzipped, just send it directly to me.) I was going to use the debug > output from the earlier thread to generate those C files, but yeah, > there are some additional bits needed. If nothing else, it would be > good to improve the diagnostics for that script.Here's the output (attached). I interrupted the process, but it continues looping forever. Kind regards. -------------- next part -------------- A non-text attachment was scrubbed... Name: debug.log Type: text/x-log Size: 5140 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20131227/61093f9f/attachment.bin>
On Dec 26, 2013, at 10:28 PM, Ariel Wainer wrote:> On 27/12/13 00:06, Charles Lepple wrote: >> Could you please send the debug output? (if it is more than ~ 30KB >> gzipped, just send it directly to me.) I was going to use the debug >> output from the earlier thread to generate those C files, but yeah, >> there are some additional bits needed. If nothing else, it would be >> good to improve the diagnostics for that script. > > Here's the output (attached). I interrupted the process, but it > continues looping forever. > > Kind regards. > <debug.log>There is a very proof-of-concept-y driver (nutdrv_atcl_usb) in the atcl branch in GitHub. We can probably remove a bunch of the retry loops that it inherited from richcomm_usb. There should also be a tarball here fairly soon: http://buildbot.networkupstools.org/public/nut/builders/Debian-x64-gcc/builds/115 -- Charles Lepple clepple at gmail