On Sat, Apr 20, 2013 at 1:56 PM, NicoBats wrote:
> so if both WINUSB and libusbK works fine, what is the purpose to use one
> over the other.
As replied before, libusbK.dll provides libusbx the capability to
access device suing WinUSB, libusb0.sys and libusbK.sys driver.
libusb0.sys and libusbK.
Le 19/04/13 01:41, Xiaofan Chen a écrit :
> On Thu, Apr 18, 2013 at 8:52 PM, NicoBats wrote:
>>> No libusbx will use libusbK.dll by default if it is present. If it is
>>> not present, libusbx will then fall back to WinUSB only mode
>>> where libusb0.sys/libusbk.sys will not be supported.
>>>
>>> Y
Le 19/04/13 01:41, Xiaofan Chen a écrit :
> On Thu, Apr 18, 2013 at 8:52 PM, NicoBats wrote:
>>> No libusbx will use libusbK.dll by default if it is present. If it is
>>> not present, libusbx will then fall back to WinUSB only mode
>>> where libusb0.sys/libusbk.sys will not be supported.
>>>
>>> Y
On Thu, Apr 18, 2013 at 8:52 PM, NicoBats wrote:
>> No libusbx will use libusbK.dll by default if it is present. If it is
>> not present, libusbx will then fall back to WinUSB only mode
>> where libusb0.sys/libusbk.sys will not be supported.
>>
>> You can ask your friend to upgrade libusbK to its
Xiaofan,
thanks for your inuput...
Le 18/04/13 07:28, Xiaofan Chen a écrit :
> On Tue, Apr 16, 2013 at 8:00 PM, nico wrote:
>> sorry to be late on that...
>> according to the first line of the user's log, libusbx try to use libusbK
>> drivers instead of WINUSB ones:
>>
>> [ 0.00] [1450] l
On Tue, Apr 16, 2013 at 8:00 PM, nico wrote:
> sorry to be late on that...
> according to the first line of the user's log, libusbx try to use libusbK
> drivers instead of WINUSB ones:
>
> [ 0.00] [1450] libusbx: debug [libusb_init] created default context
> [ 0.00] [1450] libusbx:
On Wed, Apr 17, 2013 at 11:30 PM, nicolas bats wrote:
> So, my friend tried with another computer with Vista32 and everything where
> fine (WinUSB driver installation with zadig.exe as long as find_all).
> so I guess it is a driver installation issue.
Install libusbK and then see if you find prob
So, my friend tried with another computer with Vista32 and everything where
fine (WinUSB driver installation with zadig.exe as long as find_all).
so I guess it is a driver installation issue.
++
Nicolas
2013/4/16 nico
> Hi,
> sorry to be late on that...
> according to the first line of the us
Hi,
sorry to be late on that...
according to the first line of the user's log, libusbx try to use
libusbK drivers instead of WINUSB ones:
[ 0.00] [1450] libusbx: debug [libusb_init] created default context
[ 0.00] [1450] libusbx: debug [libusb_init] libusbx v1.0.14.10576
[ 0.000
On Sat, Apr 13, 2013 at 2:43 PM, nico wrote:
>> You should use the 1.0.15rc3 since 1.0.14 has potential problem
>> with USB composite device.
>
> the user have tried with the 15rc3 with the same result (the device is a
> 0x0403, 0x6001)
You can see from my run log that I have a FTDI device with
V
On 2013.04.13 07:43, nico wrote:
C:\users\...\bin>find_all.exe
Number of FTDI devices found: 1
Checking device: 0
ftdi_usb_get_strings failed: -4 (libusb_open() failed)
A libusb_open() issue is most likely a driver installation problem.
I tested on Vista 32 with the RC3 binaries and cannot see
Hi
Le 13/04/13 05:40, Xiaofan Chen a écrit :
> On Fri, Apr 12, 2013 at 11:06 PM, nico wrote:
>> using libusbx-1.0.14 and libftdi (the problem is similar with 1.0.15-rc3)
>> downloaded from http://mcuee.blogspot.fr/ (Xiaofan's blog _ the devKit)
>> here's a report of a user that run Vista 32bits
>>
On Sat, Apr 13, 2013 at 11:40 AM, Xiaofan Chen wrote:
> On Fri, Apr 12, 2013 at 11:06 PM, nico wrote:
>> using libusbx-1.0.14 and libftdi (the problem is similar with 1.0.15-rc3)
>> downloaded from http://mcuee.blogspot.fr/ (Xiaofan's blog _ the devKit)
>> here's a report of a user that run Vista
On Fri, Apr 12, 2013 at 11:06 PM, nico wrote:
> using libusbx-1.0.14 and libftdi (the problem is similar with 1.0.15-rc3)
> downloaded from http://mcuee.blogspot.fr/ (Xiaofan's blog _ the devKit)
> here's a report of a user that run Vista 32bits
> C:\users\...\bin>find_all.exe
> Number of FTDI dev
using libusbx-1.0.14 and libftdi (the problem is similar with
1.0.15-rc3) downloaded from http://mcuee.blogspot.fr/ (Xiaofan's blog _
the devKit)
here's a report of a user that run Vista 32bits
C:\users\...\bin>find_all.exe
Number of FTDI devices found: 1
Checking device: 0
ftdi_usb_get_strings
On Thu, Apr 11, 2013 at 9:30 PM, nico wrote:
> Hi,
> is there is any windows Vista32 restriction?
No, libusbx should work under Vista 32 bit or 64bit. Actually
it works under Windows XP x86, Vista x86/x64, Win7
x86/x64 and Windows 8 x86/x64.
--
Xiaofan
-
Hi,
is there is any windows Vista32 restriction?
++
Nicolas
Le 11/04/13 09:53, nico a écrit :
> thanx!
> ++
> nicolas
> Le 10/04/13 02:44, Pete Batard a écrit :
>> On 2013.04.09 11:39, nico wrote:
>>> can someone provide a MinGW 32bits built of the last working RC,
>> Sure. Please have a look at t
thanx!
++
nicolas
Le 10/04/13 02:44, Pete Batard a écrit :
> On 2013.04.09 11:39, nico wrote:
>> can someone provide a MinGW 32bits built of the last working RC,
> Sure. Please have a look at the -win download from:
> https://sourceforge.net/projects/libusbx/files/releases/1.0.15/binaries/
>
> The
On 2013.04.09 11:39, nico wrote:
> can someone provide a MinGW 32bits built of the last working RC,
Sure. Please have a look at the -win download from:
https://sourceforge.net/projects/libusbx/files/releases/1.0.15/binaries/
The Windows binary contains the 32 and 64 bit versions of both the
stat
Hi,
can someone provide a MinGW 32bits built of the last working RC,
thanx in advance,
best regards,
Nicolas
Le 04/04/13 21:12, nico a écrit :
> Hi,
> merci beaucoup to everyone for your work...
>
> Le 04/04/13 20:35, Pete Batard a écrit :
>> On 2013.04.04 09:27, nico wrote:
>>> Making all in libu
On 2013.04.05 02:40, Xiaofan Chen wrote:
> The sentence "Don't assume high speed for isochronous or an interval of 1
> on OS X" does not sound right. Maybe it can be changed to "Fix bInterval
> value interpretation under OS X".
>
> There is a typo in 1.0.14 changelog. The word "concurent" in "with
On Fri, Apr 5, 2013 at 3:04 AM, Pete Batard wrote:
> On 2013.04.04 14:08, Xiaofan Chen wrote:
>> The following lines should be removed,
>> https://github.com/libusbx/libusbx/commit/2ffefc04769845dcb682655a437fa604e0299683
>> + /* work around buggy devices */
>> + if (0 == interval) {
>> +int
Hi,
merci beaucoup to everyone for your work...
Le 04/04/13 20:35, Pete Batard a écrit :
> On 2013.04.04 09:27, nico wrote:
>> Making all in libusb
>> CC libusb_1_0_la-core.lo
>> core.c:1755:30: warning: use of logical '&&' with constant operand
> Thanks for the report, and the test.
> Thi
On 2013.04.04 14:08, Xiaofan Chen wrote:
> The following lines should be removed,
> https://github.com/libusbx/libusbx/commit/2ffefc04769845dcb682655a437fa604e0299683
> + /* work around buggy devices */
> + if (0 == interval) {
> +interval = 9;
> + }
> +
Oh yeah, this has been included in R
On 2013.04.04 09:27, nico wrote:
> Making all in libusb
>CC libusb_1_0_la-core.lo
> core.c:1755:30: warning: use of logical '&&' with constant operand
Thanks for the report, and the test.
This is now fixed in RC3, along with a couple minor issues.
The new RC is available from:
http://sour
2013/4/4 nico
> Hi,
> my compiler is Clang on MacOS 10.7.5.
> I run
> ./configure --disable-log --prefix=/opt/local
> make CFLAGS="-arch i386 -arch x86_64 -mmacosx-version-min=10.6"
> and here's the output:
>
> Making all in libusb
>CC libusb_1_0_la-core.lo
> core.c:1755:30: warning: us
On Thu, Apr 4, 2013 at 6:24 PM, Xiaofan Chen wrote:
> Yes you are right. If using Apple gcc, then there are no warnings.
> If using clang, then yes two warnings are generated. Tested
> under Mac OS X 10.7.5.
Another thing for Mac OS X, I probably misled Nathan on
the bInterval fix.
The following
On Thu, Apr 4, 2013 at 4:27 PM, nico wrote:
> Hi,
> my compiler is Clang on MacOS 10.7.5.
> I run
> ./configure --disable-log --prefix=/opt/local
> make CFLAGS="-arch i386 -arch x86_64 -mmacosx-version-min=10.6"
> and here's the output:
>
> Making all in libusb
>CC libusb_1_0_la-core.lo
Hi,
my compiler is Clang on MacOS 10.7.5.
I run
./configure --disable-log --prefix=/opt/local
make CFLAGS="-arch i386 -arch x86_64 -mmacosx-version-min=10.6"
and here's the output:
Making all in libusb
CC libusb_1_0_la-core.lo
core.c:1755:30: warning: use of logical '&&' with constant ope
Hi,
The 2nd release candidate for libusbx v1.0.15 is now available at
http://sourceforge.net/projects/libusbx/files/releases/1.0.15/source/
This version brings the following improvements:
* Improve tranfer cancellation and avoid short read failures on broken
descriptors
* Filter out 8-bit cha
30 matches
Mail list logo
