On Wed, Jun 24, 2009 at 12:19 PM, Orin Eman<orin.e...@gmail.com> wrote:
> On Mon, Jun 22, 2009 at 7:02 PM, Xiaofan Chen <xiaof...@gmail.com> wrote:
>>
>> On Tue, Jun 23, 2009 at 3:30 AM, Duane Ellis<open...@duaneellis.com>
>> wrote:
>>
>> > All is not rosy and perfect, "WinUSB" would require an INF file that
>> > *points* to the driver - much like the work that Freddy is working
>> > towards with a universal libusb inf file
>>
>> Stephan Meyer (libusb-win32) user see WinUSB as the possible solution
>> for 64bit Windows as well. That is why he added the WinUSB backend
>> to libusb-win32 1.0 development branch. Unfortunately it is not working
>> yet.
>> The libusb-win32 WinUSB backend simplifies the use of WinUSB.
>
> I wouldn't agree with that.  In terms of ease of use, libusb and WinUSB are
> about the same.  I've just ported some code (which originally used
> propriatary drivers, then was ported to WinUSB) to libusb on linux and MAC.
> I didn't find libusb easier than WinUSB.  Then libusb on linux has the
> problem with short packets on bulk reads which WinUSB doesn't have.
>
> Now if libusb provided device arrival/removal notifications for all OSs,
> that would make it easier on all three systems.
>

I see. Since I only barely know C and got headache looking at the long API
names of Windows API calls (including WinUSB), I feel libusb is easier. ;-)

But I agree that WinUSB should not be too difficult for Windows programmers.
I've seen quite some examples to know that. A WinUSB backend without
libusb is also possible for OpenOCD. It is a very good alternative for
XP/vista/Windows 7 32bit and 64bit.

libusb-win32 can still be a viable alternative for Windows 2k/XP. Who
are still using 98SE or even Windows ME? ;-)

Last time we compared generic drivers like WinUSB and libusb-win32,
both have its advantages. For example, WinUSB does not support
isochronous transfer and does not support Windows 2k and lower.
libusb-win32 does not support Vista 64.


-- 
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