hey there,<br><br><div class="gmail_quote">2009/10/10 Kjell Claesson <span dir="ltr"><<a href="mailto:kjell.claesson@epost.tidanet.se">kjell.claesson@epost.tidanet.se</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Greg,<br>
<div class="im">> Hi Arnaud,<br>
><br>
> I must be doing something wrong.<br>
><br>
> I pulled down revision 2015 and even browsed through<br>
> <a href="http://svn.debian.org/wsvn/nut/trunk/?rev=0&sc=0" target="_blank">http://svn.debian.org/wsvn/nut/trunk/?rev=0&sc=0</a> and drivers/bcmxcp.c<br>
> shows driver version 0.22.<br>
><br>
</div>Yep, think that Arnaud missed to change the number.<br>
But he should change the usb subdriver number to 0.18 instead.<br>
<br>
The main numbering 0.22 is for the protocol part, that is the same for<br>
usb and serial. </blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The changes was made to a included function file nut-usb, that have no<br>
revision number. But it is only the usb part of bcmxcp that use this file.<br></blockquote><div><br>in fact, there are 2 things:<br>- the first is that I should really merge nut_usb into bcmxcp_usb...<br>in order not to forgot to update the communication sub driver version.<br>
so, it should indeed be 0.18 <br>- the 2nd is that I have a local uncommited change on the core (0.23...)<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">
> I can't seem to pull down a file with version 0.23.<br>
><br>
> In my last post I ran from /usr/local/ups/bin/bcmxcp_usb but I had copied<br>
> the compiled file there.<br>
><br>
> Could you possibly explain what im doing wrong or even send me a tar file<br>
> of the source?<br>
</div><br>You can run the driver in debug mode directly from the build. So when you have<br>
compiled you can call /path/to/nut/drivers/bcmxcp_usb -DD -a<ups>.<br>
The you don't have to move it for testing.<br>
<br>
What is the outcome of the debug run ?<br>
Same problems?<br>
<font color="#888888"></font></blockquote><div><br>the issue is now a short read.<br>I've had a look at LanSafe for Linux, and it's looping on interrupt_read() until the timeout or the end of the block (ignoring USB null padding).<br>
I currently to have much time to do so, but bcmxcp_usb->get_answer() should be modified.<br><br></div></div>cheers,<br clear="all">Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://www.eaton.com/mgeops">http://www.eaton.com/mgeops</a><br>
Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>Debian Developer - <a href="http://www.debian.org">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br>
<br>