On Sat, Jun 27, 2009 at 6:14 AM, Zach Welch<z...@superlucidity.net> wrote:
> On Fri, 2009-06-26 at 11:15 -0400, Duane Ellis wrote:
>> Zach Welch wrote:
>> > Only libusb+libftdi serves our long-term interests.
>> >
>> Wrong.
>>
>> "libusb" is a *blocking* issue that we cannot control, fix, nor
>> whatever. LIBUSB is not supported by *newer* windows platforms. Unless
>> and until it is supported it becomes a dead end solution, period, end of
>> story.
>>
>> I believe the "WinUSB" solution is a solution, that for some reason
>> keeps being left off your list.
>>
>> http://msdn.microsoft.com/en-us/library/aa476426.aspx
>
> I am not ignoring it.  I remember reading on another thread that WinUSB
> support has been added to libusb-win32 SVN?  If that is true, than I
> have covered your option in mine, but OpenOCD will use the same API.

Yes that the WinUSB backend support is in the SVN which is 22 months old.
I believe that the author still wants to finish it but I do not know
the timeframe.

On the other hand, it may be easier to create a WinUSB backend for
OpenOCD which covers the needs for OpenOCD (or libftdi) and
OpenOCD (or libftdi) only. You may not need to be a Windows driver
developer to do this.

libusb-win32 is more generic and IMHO you really need to be a good
Windows driver developer to make the WinUSB backend happen.
WinUSB backend will only be one of the backend for libusb-win32.
WinUSB can not replace libusb-win32. For example, it can not
support Win2k and it does not support isochronous transfer.

WinUSB has other limitations. Here is one interesting one. I am
not sure about the implications though.

The following are answers from Jan Axelson.
https://www.usb.org/phpbb/viewtopic.php?t=14353&view=next
" winusb.sys supports multiple handles, but the winusb.dll API
supports a single open handle."

https://www.usb.org/phpbb/viewtopic.php?p=47636
"I believe multiple devices are supported but not multiple
handles to the same device."



-- 
Xiaofan http://mcuee.blogspot.com
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to