libftdi Archives

Subject: Re: Use libusb 1.0

From: Xiaofan Chen <xiaofanc@xxxxxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Date: Mon, 10 Aug 2009 10:22:49 +0800
On Mon, Aug 10, 2009 at 10:16 AM, Michael
Plante<michael.plante@xxxxxxxxx> wrote:
>>> So even libusb-win32 1.0 is finished, it is not compatible with
>>> libusb 1.0. And currently there is no porting work being done
>>> to port libusb 1.0 to Windows.
>
> I was trying to understand the difficulty involved in that porting work.  Is
> the driver portion sufficiently flexible that it could be left alone, if
> someone decided to make that port?

I am not sure here. I think the kernel driver is flexible enough. It
is just a generic driver. Maybe some more ioctl is necessary.
But I am not sure.

The user space DLL may need major changes.

Anyway, you are welcome to start porting libusb 1.0 to
Windows, using codes in libusb-win32 as a base may
be a good idea. Or you can start from scratch, using
WinUSB as the backend (giving up support of isochronous
transfer).

In the case of libftdi, it is possible to stay with libusb-win32
0.1 and yet support async mode since libusb-win32 0.1
already supports async mode (not well documented though).

-- 
Xiaofan http://mcuee.blogspot.com

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx

Current Thread