Faster than I expected, I've become somewhat disenchanted by the openups-usb driver.
So, if I write my own subdriver for our UPS...how quickly can I expect that it will be incorporated in some downloadable version of nut that a user can then use? The main reason I ask is because I have to include a guide for getting the UPS to work in Linux. If I can simply stipulate that they have to download NUT version 2.xx.xx and the driver will be included, then that makes things a lot easier than having to provide the driver ourselves along with the procedure for them to add it to the NUT source, etc. I'm not talking about in a package, I mean just a part of the sources that they can download, extract, compile, install. I have just under two months to have a guide a customer can use to make the UPS shutdown their Linux PC. If that won't be enough time to get something into the NUT trunk, then I'll have to make-do with the openups-usb driver, and work our own driver later. I've read through the 3.9 Source Code Management section of the dev guide. I'm much more familiar with svn than git, though I know that needs to change. Sincerely, Rob Groner Software Engineer RTD Embedded Technologies, Inc. ISO9001 and AS9100 Certified Ph: 814-234-8087 www.rtd.com<http://www.rtd.com/>
_______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
