Re: [Nut-upsdev] Embedding man pages in driver source code

2009-09-04 Thread Charles Lepple
On Thu, Sep 3, 2009 at 12:37 PM, Arnaud Quetteaquette@gmail.com wrote: 2009/9/2 Charles Lepple clep...@gmail.com With the AsciiDoc conversion underway, I am wondering if we should keep the AsciiDoc for the driver man pages in a specially-formatted comment in the driver (taking a cue from

Re: [Nut-upsdev] Embedding man pages in driver source code

2009-09-04 Thread Stuart D. Gathman
On Fri, 4 Sep 2009, Arnaud Quette wrote: while I clearly see the advantage of moving manpages to AsciiDoc (allow to generate html... output), I still don't much see the one of embedding it with the code. perhaps you, as the one who has practiced it, can shed my light. I'd also like to hear

Re: [Nut-upsdev] ups_set_altinterface() breaks tripplite_usb on Mac OS X

2009-09-04 Thread Arnaud Quette
2009/9/3 Charles Lepple clep...@gmail.com On Sep 3, 2009, at 9:22 AM, Arnaud Quette wrote: The codeless kext stuff is not too complicated - we could probably generate them the same way as the udev configuration files. The only trick is that the USB VID, PID, bConfigurationValue,

Re: [Nut-upsdev] FreeBSD, NUT OmniVS1500

2009-09-04 Thread Charles Sprickman
On Fri, 4 Sep 2009, Charles Lepple wrote: Hi Charles, On Sep 4, 2009, at 9:00 PM, Charles Sprickman wrote: USB error: could not set alt intf 0/0: Invalid argument Interesting that you should mention this. It came up just the other day regarding Mac OS X: