<html>
<body>
<font size=3>Alexander,<br>
I have tried stopping and starting the driver a couple of
times and it all seems to work OK. No error messages.<br><br>
As for using the usb_control_msg, the details on using it
seem a little obscure. I think you have to read the HID manual and then
guess. The online help in the libusb-devel is next to useless, as it does
not describe the parameters or their settings. Anyway, if you have the
details of how to use this call then can you let me have a copy so that I
can better understand it.<br><br>
Regards<br>
Jon<br><br>
At 09:27 3/02/2007, Alexander I. Gordeev wrote:<br>
<blockquote type=cite class=cite cite="">Hi Jon,<br><br>
Jon wrote:<br>
> Alexander,<br>
> I have just done a test with your code and
it does work. <br><br>
My primary concern is an error, I was talking about in my previous<br>
posts.<br>
Did you have it?<br>
It only appears when you start the driver, then stop it and start it<br>
again.<br><br>
> I was doing my work on the latest stuff from
SVN to see if that<br>
> would help in my investigations. I did not apply the patches
from<br>
> previous mails, just used the code in the later modules (the patch
process produced errors).<br><br>
> It does not matter which version we use as
both work for me,<br>
> now. We just need to implement a few more commands into your
code,<br>
> if we use that, and work out how to implement the code that
sends<br>
> data to the UPS, ie the S<n>, S<n>R<m> and
T<n> commands. I also<br>
> want to implement the TL, C and CT commands, but I whilst I
can see<br>
> the reaction to these it is a little difficult to work out the code
to use.<br><br>
I'll try to figure it out. usbsnoop will help me
<img src="http://messenger.msn.com/MMM2004-08-11_11.52/Resource/emoticons/regular_smile.gif" width=19 height=19 alt="Smiley"><br><br>
> I think the F command may need a little more
work as I think it<br>
> may need to issue the '0x01' command first to get the
manufacturer.<br><br>
I think it won't be very hard to make it universal for both our<br>
devices.<br><br>
> Anyway, both sets of code work, for me at
least, so it is up to<br>
> the powers that be to decide which way to go.<br><br>
It's no need to throw away any code.<br>
Since you've already written a working driver it can be used as
well.<br>
I think we should merge our subdrivers into one.<br><br>
Jon wrote:<br>
> Peter,<br>
> The only changes that were needed was the
addition of the<br>
> get/set Ablerex code, or the using of the Krauler stuff for
Ablerex.<br>
> The 'usb_get_string_simple' does the same job as<br>
> 'usb_get_descriptor', the former just has one less parameter,
and<br>
> during my investigations the simpler the better.<br><br>
Thwy are slightly different as I know. Anyway I have a plan to
change<br>
'usb_get_descriptor' to 'usb_control_msg' to test if it can help to<br>
reduce "USB No Ack" responses. There is yet another parameter
you can<br>
specify in that function - timeout. I tnik, it could help.<br><br>
-- <br>
Alexander
<a href="mailto:lasaine@lvk.cs.msu.su" eudora="autourl">
mailto:lasaine@lvk.cs.msu.su</a></font></blockquote>
<BR><BR>
<TABLE width=400><HR>
<P style="FONT: 9pt/11pt verdana"><a href="http://www.avast.com">avast! Antivirus</a>: Outbound message clean.
<P style="FONT: 8pt/11pt verdana">Virus Database (VPS): 000709-2, 01/02/2007<BR>Tested on: 3/02/2007 10:41:30 AM<BR><FONT color=gray>avast! is copyright (c) 2000-2007 ALWIL Software.</FONT></P>
<TBODY></TBODY></TABLE>
<BR>
</body>
<br>
</html>