| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
* also added -j2 to _bm.sh
|
|
|
|
|
|
|
| |
* unlike later iterations of Visual Studio, MSVC6 does not accept
blank parameters on macro calls [eg. CALL(a, ,b)]
* blank params were used with the DLL_DECLARE and DLL_LOAD macros
* issue reported by Satz Klauer
|
|
|
|
|
|
| |
* easier to spot comments
* simplify errors through the use of a %PWD%
* used a BUILD_CMD variable with updated options
|
|
|
|
| |
* display bluetooth addresses of controller and master
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
* uint32_t* being caset to int*
* simplify allocation using calloc
* fix VS2010 Intellisense warnings
|
|
|
|
|
|
| |
* add missing warning on alloc failure
* prefer calloc() to malloc()
* add casts to address VS2010 IntelliSense warnings
|
|
|
|
|
| |
* note that WinUSB prevents proper use of LIBUSB_RECIPIENT_INTERFACE
for Extended Properties: http://www.lvr.com/forum/index.php?topic=331
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
* introduced by the windres step improvement:
libusb/Makefile.am:28: pkg_v_rc_$(V: non-POSIX variable name
libusb/Makefile.am:29: pkg_v_rc_$(AM_DEFAULT_VERBOSITY: non-POSIX variable name
|
|
|
|
| |
* reverts 3209815810a7e1deb6cb961a4dac01b9cfb64d7d
|
|
|
|
| |
* reverts 52925893448df74e895d756c3280af15494d4166
|
| |
|
|
|
|
|
| |
* indexes were outgrowing the array before realloc,
resulting in out of bound access and crash.
|
|
|
|
|
|
| |
* These descriptors are used for automated WinUSB driver
installation on Windows 8
* http://msdn.microsoft.com/en-us/library/windows/hardware/hh450799.aspx
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
* also trailing whitespaces and formatting
|
|
|
|
| |
* MinGW was issuing a "suggest parenthesis" warning with timercmp
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
* fixed typos and missing breaks
* device_speed in .def
* device_speed in xusb
|
| |
|
| |
|
|
|
|
| |
[stuge: Formatting fixes and split out libusb_get_device_speed() change]
|
|
|
|
|
|
| |
* use (currently superspeed unaware) USB_NODE_CONNECTION_INFORMATION_EX
[stuge: Explicitly convert OS device speeds to libusb device speeds]
|
|
|
|
| |
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reworked version of my earlier patch, largely modelled after (if not
copy and pasted from) Trygve Laugstøl's <trygvis@inamo.no> similar
commit 5a6541e0d80fb1f21e2b960bc2337a612f9d74fb in
git://git.libusb.org/libusb-trygvis.git
http://git.libusb.org/libusb-trygvis.git
http://git.libusb.org/?p=libusb-trygvis.git;a=commitdiff;h=5a6541e0d
This patch does not add any OS specific code. The supporting code in
each backend follows in separate patches.
Signed-off-By: Hans de Goede <hdegoede@redhat.com>
|
|
|
|
|
|
| |
Remove code duplication.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
|
|
|
|
|
|
| |
On Linux we often need to read (postive) integers from sysfs. This patch
adds a helper function for this. This is a preparation patch for adding
a libusb_get_device_speed() function to libusb.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When an interface is bound to the usbfs driver (iow claimed), the
kernel will unbind it, and then after the reset do a device_attach
on the interface, which will bind the default in kernel driver to
the interface.
So if an app has detached the in kernel driver, and claimed the
interface and then does a libusb_reset_device. Things end up with
the interface no longer being bound to the usbfs driver (so no longer
claimed) and instead it is bound to the in kernel driver (iow the in
kernel driver is re-attached).
We can stop this from happening by releasing all claimed interfaces
before the reset, as the kernel will not do the device attach after
reset, if no driver was bound to the interface before the reset.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
|
|
|
|
|
|
|
| |
claimed_interfaces is a long and thus its size differs on 32
versus 64 bits, this patch uses USB_MAXINTERFACES instead of
sizeof(claimed_interfaces) on interface number range checks
for consistent behavior independent of the arch.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Compiling with gcc-4.6 results in the following warnings:
os/linux_usbfs.c: In function 'op_get_configuration':
os/linux_usbfs.c:1144:6: warning: variable 'r' set but not used ...
os/linux_usbfs.c: In function 'op_handle_events':
os/linux_usbfs.c:2091:40: warning: 'status' may be used uninitialized ...
os/linux_usbfs.c:2044:6: note: 'status' was declared here
dpfp.c: In function 'save_to_file':
dpfp.c:228:9: warning: variable 'ignore' set but not used ...
dpfp_threaded.c: In function 'save_to_file':
dpfp_threaded.c:257:9: warning: variable 'ignore' set but not used ...
This patch fixes these. (The second comes from handle_control_completion()
which gcc seems to inline into op_handle_events().)
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
[stuge: Add fixes for dpfp examples and update source references]
|
| |
|
|
|
|
|
|
|
| |
Remove the test that sets the flag since GNU89 inline semantics are not
required by libusb.
[stuge: Also remove reference to the test result]
|
| |
|
| |
|
|
|
|
| |
References #28.
|