Changes between Version 33 and Version 34 of windows_backend

Timestamp:

02/17/10 19:01:22 (7 months ago)

Author:

pbatard

Comment:

--

windows_backend

@@ -7 +7 @@
 == Status ==
 
-The Windows backend is now in beta stages. As of 2010.01.13, it should include the main libusb v1.0 features, apart from isochronous transfers (which is a limitation from the WinUSB Microsoft API) and concurrent access support.[[BR]]
-It currently supports all Windows platforms from Windows XP, including 64 bit versions of Windows (untested on Windows 2003).
+The Windows backend is now in pre-release stages. As of 2010.02.17, it include all of the main libusb v1.0 features, for both HID and WinUSB devices, apart from isochronous transfers (which is a limitation from the WinUSB Microsoft API).[[BR]]
+It currently supports all Windows platforms from Windows XP, including 64 bit versions of Windows (Windows 2003 is untested).
 
 == Source ==
@@ -23 +23 @@
 Note that before you can install [http://code.google.com/p/tortoisegit/ TortoiseGit] you need to install [http://code.google.com/p/msysgit/ MSysGit] and make sure that, during the installation of MSysGit, when prompted to adjust the PATH environment, you select "Run Git from the Windows Command Prompt" (2nd option). Also, in the general settings of [http://code.google.com/p/tortoisegit/ TortoiseGit], the MSysGit path must point to the MSysGit bin directory (eg: C:\Program Files (x86)\Git\bin")
 
-To compile this source, [http://sourceware.org/pthreads-win32/ pthread-win32] is also required, '''except for cygwin''', where pthread should be available by default.[[BR]]
-For convenience, precompiled versions of pthread-win32 for 32 bit and 64 bit Windows platforms are provided [http://libusb.org/raw-attachment/wiki/windows_backend/pthread-win32_libusb.zip here].
+Also note that, for MinGW and cygwin, as per the official libusb 1.0 project, '''you need to run './autogen.sh' in order to have configure and Makefile created for you'''.
+
+To compile this source, [http://sourceware.org/pthreads-win32/ pthread-win32] is also required, '''except for cygwin''', where pthread should be available by default. Note that the version of the DLL you should use is VC2, '''not GC'''[[BR]]
+For convenience, precompiled versions of pthread-win32 for 32 bit and 64 bit Windows platforms are provided [http://libusb.org/raw-attachment/wiki/windows_backend/pthread-win32_libusb.zip here]. If you are unfamiliar with pthread to use, please download this archive.
 
 The following development environment are currently supported for libusb 1.0 on Windows:
@@ -43 +45 @@
   * Because Windows does not provide a native poll() function, and cygwin is the only development environment that provides such a call, the use of libusb file descriptors with poll() on cygwin is '''NOT''' supported. If you do need to manually poll the libusb file descriptors on Windows, you can use the undocumented _libusb_poll() function (same parameters as poll() on UNIX), but please note that the function will only accept libusb file descriptors and it is not possible to _libusb_poll() to poll for generic file descriptors. We might provide native Windows Event to wait on in a future version of libusb for Windows.
 
-== Current Issues ==
+== Known Restrictions ==
 
   * IOCTL_USB_GET_NODE_CONNECTION_INFORMATION [http://sourceforge.net/tracker/index.php?func=detail&aid=2904747&group_id=202880&atid=983354 appears to be broken] in MinGW-w64 (x64 platforms).
   * WinUSB does not support multiple concurrent applications (as per the [http://download.microsoft.com/download/9/C/5/9C5B2167-8017-4BAE-9FDE-D599BAC8184A/WinUsb_HowTo.docx WinUSB Howto whitepaper]).
   * WinUSB does not support isochronous transfers.
+  * Windows does not allow read or write access to HID keyboards and mice
+  * Windows does not allow generic USB access to HID devices or interfaces for which the OS has a specific device (eg. HID audio devices)
 
 == To Do ==
 
-  * multithreading/concurrent access
-  * automated WinUSB driver installation?
+  * full pthread-win32 dependency removal
+  * automated WinUSB driver installation
   * hotplug detection
 
 == Done ==
 
+  * multithreading/concurrent access
   * HID
   * device enumeration