<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Faster than I expected, I’ve become somewhat disenchanted by the openups-usb driver. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> 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.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sincerely,<o:p></o:p></p><p class=MsoNormal>Rob Groner<o:p></o:p></p><p class=MsoNormal><b><o:p> </o:p></b></p><p class=MsoNormal><i>Software Engineer</i><o:p></o:p></p><p class=MsoNormal><b><span style='color:#A70C28'>RTD Embedded Technologies, Inc.</span></b><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt'>ISO9001 and AS9100 Certified</span></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt'>Ph: 814-234-8087</span><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><a href="http://www.rtd.com/"><span style='font-size:10.0pt;color:blue'>www.rtd.com</span></a><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>