On Wed, Aug 6, 2014 at 9:08 AM, Bob Tausworthe t...@sentons.com wrote:
Thank you for the reply. Sorry for the confusion. I am using lib usb 1.0.19.
I guess I am on the wrong mailing list. So many flavors of open source...
what is the correct list for lib usb for windows? Can I transfer the
On Wed, Feb 12, 2014 at 1:13 PM, Nothing sckal...@vip.qq.com wrote:
I use ubuntu 13.04 i build it use ./configure then make install
What is the architecture? Is it x86/x64 or ARM? You may
want to post all the build log.
--
Xiaofan
On Sat, Feb 8, 2014 at 1:13 AM, hgs16 h...@rapsodo.com wrote:
Hi all,
I am having issues when trying to use synchronous calls from multiple
threads.
From thread A I do libusb_bulk_transfer(dev_hnd,IN_EP,...) (read) and in
another thread B I do libusb_bulk_transfer(dev_hnd,OUT_EP,...)
On Sun, Jan 12, 2014 at 10:22 AM, Xiaofan Chen xiaof...@gmail.com wrote:
Nice. I just carried some simple tests under Mac OS X 10.9.1 (Mac
Mini 2011) and NetBSD 6.1.1 (VirtualBox VM) using libusbx-1.0.18-rc1
and both are fine.
For NetBSD, there are three known warnings about dereferencing
On Fri, Jan 10, 2014 at 2:17 PM, Pradeepa Senanayake
pradeepa@gmail.com wrote:
Hello all,
I have an application using libusb-win32 API and a device using libusb0.sys
driver. I wanted to check the possibility of using the newly released libusb
library in my application. So I just tried to
On Wed, Dec 25, 2013 at 12:06 AM, Nothing sckal...@vip.qq.com wrote:
Mery xmas every one
additional I want to know why I can not download the latest libusb version
libusb1.0.16 ?
dose this attach file is libusb1.0.16 32bit ? why I use so it say Hotplug
capabilites are not supported on
On Tue, Nov 26, 2013 at 12:38 PM, Nothing sckal...@vip.qq.com wrote:
if your ARM Linux distribution is ok ,can you send me the so file ? tks very
much
Sorry but I do not use ARM Linux.
Please also take note you need to subscribe to libusbx mailing list
in order to post. If not, your further
On Tue, Nov 26, 2013 at 4:41 AM, Liang Zhu l...@accu-time.com wrote:
I would like to know if the function libusb_claim_interface enables the DFU.
This question makes no sense. libusb_claim_interface has nothing
to do with DFU. What is the real problem you are trying to solve?
--
Xiaofan
On Mon, Nov 25, 2013 at 10:42 PM, Nothing sckal...@vip.qq.com wrote:
/configure --prefix=`pwd`/install --build=i686-linux --host=arm-linux
ac_cv_func_malloc_0_nonnull=yes --disable-udev --with-pic
but the result is that I use libusb 1.0.09 does not have that problem
can not support
On Tue, Nov 12, 2013 at 1:02 PM, Kustaa Nyholm
kustaa.nyh...@planmeca.com wrote:
is this list still active or has everyone moved to libusb-devel list?
This list is still active. Probably people who can answer your
question is either
on vacation or busy with other things.
--
Xiaofan
On Tue, Sep 24, 2013 at 9:25 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Sat, Sep 21, 2013 at 1:42 PM, Kano libu...@iporg.org wrote:
Since a handle is only associated with a single interface,
I must have multiple handles.
I think this is not really correct. A handle to the device
can
On Sat, Sep 21, 2013 at 10:26 AM, Kano libu...@iporg.org wrote:
In case it's a Zadig issue.
I'm running zadig_xp_v2.0.1.160 on a Windows XP VM.
I've switched all 4 interfaces to WinUSB v6.1.7600.16385
A diff of the first 2 inf files:
# diff -a Cairnsmore1_\(Interface_0\).inf
On Sat, Sep 21, 2013 at 7:21 AM, Kano libu...@iporg.org wrote:
Hi,
I've been using usb for about a year on many devices but only using a
single interface.
Finally got some hardware that has 2 interfaces and the code I've written
works on linux but fails on windows.
Anyone know if there are
On Tue, Sep 17, 2013 at 6:08 AM, Ramon Zambelli
ramon.zambe...@bluewin.ch wrote:
On 9/16/2013 3:36 AM, Xiaofan Chen wrote:
I think WinUSB version should not be the problem. Please post the
debug log (eg: xusb -d yourvid:yourpid).
The problem seems to come from my device having two interfaces
On Fri, Sep 6, 2013 at 10:52 PM, Hans de Goede hdego...@redhat.com wrote:
Signed-off-by: Hans de Goede hdego...@redhat.com
---
libusb/core.c | 2 +-
libusb/libusbi.h| 4 ++--
libusb/os/darwin_usb.c | 6 +-
libusb/os/linux_usbfs.c | 5 -
libusb/os/netbsd_usb.c
On Sat, Sep 7, 2013 at 11:36 PM, Alan Stern st...@rowland.harvard.edu wrote:
Slightly off the original topic but perhaps still relevant...
There are several Linux programs using libusb-0.1 that don't work with
libusb-compat. The reason is that they perform some or all of their
I/O using the
On Fri, Sep 6, 2013 at 6:58 PM, Hans de Goede hdego...@redhat.com wrote:
On 09/05/2013 03:14 AM, Xiaofan Chen wrote:
On the other hand, maybe we then have to document this limitation
of libusb-compat.
You mean simply document that atexit is used and apps must not make any
calls from atexit
On Sat, Aug 31, 2013 at 12:21 AM, Gisle Vanem gisle.va...@gmail.com wrote:
Good job, but there are some warnings from MSVC v16
Is that Visual C++ 2010?
when I'm
using '-Wp64' in my CFLAGS. enable 64 bit porting warnings.
I'm on a 32-bit WIndows:
libusb/core.c(692) : warning C4267: '=' :
On Fri, Aug 30, 2013 at 4:14 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Wed, Aug 28, 2013 at 5:35 PM, Hans de Goede hdego...@redhat.com wrote:
I'm very happy to announce libusbx-1.0.17-rc1.
You can download the 1.0.17-rc1 tarbal here:
http://downloads.sourceforge.net/libusbx/libusbx-1.0.17
On Wed, Aug 28, 2013 at 5:35 PM, Hans de Goede hdego...@redhat.com wrote:
I'm very happy to announce libusbx-1.0.17-rc1.
You can download the 1.0.17-rc1 tarbal here:
http://downloads.sourceforge.net/libusbx/libusbx-1.0.17-rc1.tar.bz2
Please give it a thorough testing, and report any issues
On Fri, Aug 30, 2013 at 8:47 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Fri, Aug 30, 2013 at 4:14 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Wed, Aug 28, 2013 at 5:35 PM, Hans de Goede hdego...@redhat.com wrote:
I'm very happy to announce libusbx-1.0.17-rc1.
You can download the 1.0.17
On Mon, Aug 26, 2013 at 7:32 PM, Martin Pieuchot mpieuc...@nolizard.org wrote:
But assuming there are some people crazy enough to build their
own libusbx on OpenBSD for real use instead of using the official
packages, I would bet they are running -current. OpenBSD doesn't
have a development
On Sat, Aug 24, 2013 at 10:30 AM, Juan Lang juanl...@google.com wrote:
It's not as scary as it looks, but I thought I'd first send one big patch to
show where it's headed. If it's easier I can break it up into several
different patches, something like:
1. Move initializing a device from a
On Fri, Aug 23, 2013 at 9:36 PM, Xiaofan Chen xiaof...@gmail.com wrote:
As per OpenBSD changelog, USB_DEVICE_GET_DDESC,
USB_DEVICE_GET_FDESC and USB_DEVICE_GET_FDESC
are new IOCTLs added to OpenBSD-Current beyong the current
stable 5.3 release.
Ref: http://www.openbsd.org/plus.html
I am
On Thu, Aug 22, 2013 at 10:50 PM, Hans de Goede hdego...@redhat.com wrote:
On 08/22/2013 03:30 AM, Xiaofan Chen wrote:
For OpenBSD and NetBSD, I can carry out some simple tests
over the weekend (basic building, stress test and xusb example
on a few devices).
I was already hoping you would
On Fri, Aug 23, 2013 at 2:29 AM, Juan Lang juanl...@google.com wrote:
2013/8/21 Xiaofan Chen xiaof...@gmail.com
I think in the past we have fixed a few issues for some of the Renesas
and Intel issues. Could you give more details of the USB host
controllers you are seeing the problems? And you
On Fri, Aug 23, 2013 at 9:51 AM, Pete Batard p...@akeo.ie wrote:
On 2013.08.16 04:27, Xiaofan Chen wrote:
And hopefully now Pete
or others can come out a proper fix with all the information.
I have way too much lined up, so I have to drop stuff that I know I'll
never get a chance to look
On Fri, Aug 23, 2013 at 9:30 AM, Pete Batard p...@akeo.ie wrote:
On 2013.08.22 19:29, Juan Lang wrote:
Now, considering that it's very likely that once you upgrade your
Renesas drivers, as you should have done long ago, you will also confirm
that your issue disappears, and that I can't help
On Wed, Aug 14, 2013 at 7:52 AM, Pete Batard p...@akeo.ie wrote:
On 2013.08.14 00:21, Xiaofan Chen wrote:
BTW, libusbx Windows also does not support Multiple HID
top level collections (only the first top level collection will be
used). The situation is a bit similar here.
Yeah, but I don't
On Tue, Aug 20, 2013 at 9:15 PM, Toby Gray toby.g...@realvnc.com wrote:
On 20/08/13 05:44, Anton Smirnov wrote:
While usb_device_set_open_close_func(..) is clearly suitable for the
librtlsdr-android project, I would feel that it isn't suitable as an API for
addition to libusb. I'm not a
On Mon, Aug 19, 2013 at 11:34 PM, Hans de Goede hdego...@redhat.com wrote:
Hi All,
I was hoping someone else would take care of this while I was otherwise
occupied, but alas ...
It also seems we've accumulated a little bit more then I was hoping for
when I suggested to do a quick bugfix
On Fri, Aug 16, 2013 at 4:51 PM, Hans de Goede hdego...@redhat.com wrote:
On 08/16/2013 05:34 AM, Xiaofan Chen wrote:
diff --git a/libusb/Makefile.am b/libusb/Makefile.am
index 33a609a..a20fdb5 100644
--- a/libusb/Makefile.am
+++ b/libusb/Makefile.am
@@ -5,5 +5,5 @@ libusb_la_SOURCES
On Thu, Aug 15, 2013 at 11:08 PM, kal...@interia.pl wrote:
Hi I wonder if there is any function which lock or unlock chosen
pnedrive. Should I interferee with usb controller?
I would like to decide which pendrive is limited or not.
Any ideas?
Every sugestion is welcome
Firstly this has
On Wed, Aug 14, 2013 at 10:05 PM, Hans de Goede hdego...@redhat.com wrote:
From: Daniel Berrange berra...@redhat.com
Since libusb-0.1 did not have any init / exit function, code using the
libusb-0.1 API will not call libusb_exit.
Hmm, it that true with the latest libusb-compat-0.1.5? As per
On Wed, Aug 14, 2013 at 3:23 PM, luis morales
luis.mora...@servexternos.isban.es wrote:
Dear All,
I need to know if it is possible this points:
1-To execute an unattended installation of libusb in a windows 7 OS (32
bits)
2-I need that the driver be signed.
I executed inf - wizard and I
On Wed, Aug 14, 2013 at 2:46 PM, Jan Becvar j...@groget.org wrote:
On 14-Aug-13 1:52, Pete Batard wrote:
As far as WinUSB is concerned, I think the best we can get is
WinUsb_GetAssociatedInterface(), but that what we're already trying to
use.
I saw this call in winusbx_claim_interface, but
On Thu, Aug 15, 2013 at 12:45 AM, Tim Roberts t...@probo.com wrote:
Pete Batard wrote:
On 2013.08.14 00:21, Xiaofan Chen wrote:
The 2nd option is not possible without changes in libusbx. Right now
it is not possible to access the other interfaces other than the first
interface in an interface
On Tue, Aug 13, 2013 at 4:36 PM, Jan Becvar j...@groget.org wrote:
Hi everybody,
I have a question about a possible problem of accessing composite
devices using interface association from libusbx. Not sure, but the
problem might be related to the maling list thread
libusb_claim_interface()
On Tue, Aug 13, 2013 at 9:53 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Tue, Aug 13, 2013 at 6:15 PM, Jan Becvar j...@groget.org wrote:
From my understanding of MS documentation related to IAD's handling, e.g.
http://msdn.microsoft.com/en-us/library/windows/hardware/ff537107%28v=vs.85%29
On Tue, Aug 13, 2013 at 4:36 PM, Jan Becvar j...@groget.org wrote:
Hi everybody,
I have a question about a possible problem of accessing composite
devices using interface association from libusbx. Not sure, but the
problem might be related to the maling list thread
libusb_claim_interface()
On Tue, Aug 13, 2013 at 6:15 PM, Jan Becvar j...@groget.org wrote:
On 13-Aug-13 11:36, Xiaofan Chen wrote:
As replied by Tim in that thread, each interface of a USB composite
device is a separated one. If you only installed the supported driver for
the first interface, (Interface 0), then you
On Tue, Aug 13, 2013 at 10:40 PM, Jan Becvar j...@groget.org wrote:
On 13-Aug-13 16:16, Xiaofan Chen wrote:
Hmm, I am not be totally correct. I just tried one USB Web
Camera which is an IAD device, the first collection has two
interfaces (Interface count =2, Interface and Interface 1
On Wed, Aug 14, 2013 at 2:26 AM, Pete Batard p...@akeo.ie wrote:
Hi Jan,
On 2013.08.13 16:15, Jan Becvar wrote:
Forgot to add that my idea/hope was that libusbx, when setting backend
of a composite interface, could check if this is not by chance first
interface of an IAD-collection and if
On Wed, Aug 14, 2013 at 3:48 AM, Jan Becvar j...@groget.org wrote:
The composite parent workaround is good enough for me in the moment, it
just might become limiting in the future, that's why I raised the
question...
The question is perfectly legitimate. The solution on the other
hand, will
On Mon, Aug 12, 2013 at 8:08 PM, Toby Gray toby.g...@realvnc.com wrote:
I assume it'd be helpful for others to have this information recorded
somewhere. Would a wiki page or an update to the README be
more appropriate?
I think Android has become so popular that a README.Android
is good to
Just tried VS2012 under Windows 8 and there is a warning
for latest git tree. It is probably better to fix this as well for
1.0.17 release.
..\libusb\os\windows_usb.c(1768): warning C4267: 'return' : conversion
from 'size_t' to 'int', possible loss of data
--
Xiaofan
FYI.
On Mon, Aug 12, 2013 at 1:18 AM, Travis libusbdot...@gmail.com wrote:
Greetings,
libusbK v3.0.6.0 has just been released:
https://sourceforge.net/projects/libusbk/files/libusbK-release/3.0.6.0/
In the past releases have also been available on Google code but this
will no longer be the
On Fri, Aug 9, 2013 at 6:51 PM, Toby Gray toby.g...@realvnc.com wrote:
If you are planning on testing on a device then you'll need to have root
access to it or fiddle around with building custom ROMs to setup
permissions on /dev/bus/usb/*/*.
Also be aware that the Android dynamic loader is
On Mon, Aug 5, 2013 at 7:39 AM, Pete Batard p...@akeo.ie wrote:
On 2013.08.04 07:46, Hans de Goede wrote:
So I may be misremembering things, as the data we seem to derive from
the first IOCTL isn't used for the topology, but to cache the actual
config descriptor (which libusb mandates us to
To libusbx mailing list as well.
-- Forwarded message --
From: Paul Fertser fercer...@gmail.com
Date: Sat, Aug 3, 2013 at 3:04 AM
Subject: [libusb] [PATCH] libusb-compat: mingw cross-compilation fixes
To: libusb-de...@lists.sourceforge.net
Cc: Paul Fertser fercer...@gmail.com
On Fri, Aug 2, 2013 at 6:02 PM, Hans de Goede hdego...@redhat.com wrote:
On 08/02/2013 10:23 AM, Martin Pieuchot wrote:
I'm sorry but this backend is not supposed to be built outside OpenBSD,
it's not tested, not debugged and I have no plan to do so. If someone
wants to support a backend for
On Tue, Jul 30, 2013 at 11:38 PM, Hans de Goede hdego...@redhat.com wrote:
Hi Martin,
On 07/16/2013 11:32 AM, Martin Pieuchot wrote:
Hello Hans and Pete,
You'll find below an update for OpenBSD's libusb backend, freshly
rebased on top of the last libusb/libusbx release.
I sent it twice to
On Wed, Jul 31, 2013 at 4:40 PM, Hans de Goede hdego...@redhat.com wrote:
By the way, since my understanding is that you were the one who modified
the libusb.org downloads, can you please add a note about the merging as
requested by
On Wed, Jul 31, 2013 at 5:25 AM, Pete Batard p...@akeo.ie wrote:
On 2013.07.30 20:24, Nathan Hjelm wrote:
I will keep this
branch in sync with the master. When do we want to make the official
switch? 1.0.18?
There will be some more Windows related changes related to the libusbx
- libusb
On Sat, Jul 27, 2013 at 10:45 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Sat, Jul 27, 2013 at 12:04 AM, jakubon2 ondrej.jaku...@nsl.eu.com wrote:
Or alternatively,
does it mean I should revert in Git to the version of old /libusb/ (=not
/libusbx/)?
Since you do not need hotplug support
On Thu, Jul 25, 2013 at 4:04 PM, Egli, Samuel samuel.e...@siemens.com wrote:
Hi all,
I want to report (what I belief is) a bug on the windows implementation of
libusbx.
The issue arose using dfu-util (which uses libusbx) when changing from an
older
U-Boot version (v2011-09) to the
On Thu, Jul 25, 2013 at 12:52 AM, Juan Lang juanl...@google.com wrote:
Hi there,
I've got a little test program that I'm running against a device I have,
which is supported by the winusb driver.
...
Naturally it succeeds when the device is inserted in a USB 2.0 port. I've
verified the
On Wed, Jul 24, 2013 at 7:40 PM, jakubon2 ondrej.jaku...@nsl.eu.com wrote:
Hi there, I am reporting the same problem with Xilinx Linux for ARM. I am
calling:
TOOLCHAIN=/opt/Xilinx/14.3/ISE_DS/EDK/gnu/arm/lin64/arm-xilinx-linux-gnueabi
PATH=$PATH:$TOOLCHAIN/bin
On Fri, Jul 12, 2013 at 3:14 PM, Hans de Goede hdego...@redhat.com wrote:
On 07/12/2013 12:15 AM, Pete Batard wrote:
Finally, the default download from SF was set to the windows binaries,
which is not what we want, especially as we always use the default SF
download for the latest source on
On Wed, Jul 10, 2013 at 1:50 PM, igx deepak igx...@gmail.com wrote:
Hi All,
If the function libusb_open_device_with_vid_pid() is used for a Composite
device exposing multiple interfaces, will it open the composite device or a
particular interface??
Please read the libusbx API documents.
Ref:
On Thu, Jul 4, 2013 at 5:14 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Wed, Jul 3, 2013 at 3:29 AM, Sean McBride s...@rogue-research.com wrote:
On Tue, 2 Jul 2013 23:18:12 +0400, Paul Fertser said:
What about documenting this in some special API bugs file or
documentation section?
We should
On Sat, Jul 6, 2013 at 3:15 PM, Hans de Goede hdego...@redhat.com wrote:
I'm very happy to announce libusbx-1.0.16-rc3.
Just carried out some quick tests under Mac OS X, Windows 8
x64 VM and OpenBSD 5.2 VM, all are okay.
--
Xiaofan
On Wed, Jul 3, 2013 at 3:29 AM, Sean McBride s...@rogue-research.com wrote:
On Tue, 2 Jul 2013 23:18:12 +0400, Paul Fertser said:
What about documenting this in some special API bugs file or
documentation section?
We should definitely have a bug for make libusb -Wcast-align safe...
Would you
On Tue, Jul 2, 2013 at 10:11 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Mon, Jul 1, 2013 at 7:14 PM, Hans de Goede hdego...@redhat.com wrote:
You can find 1.0.16-rc2 docs including all the new API-s here:
http://people.fedoraproject.org/~jwrdegoede/libusb-reference/
One issue here:
http
On Wed, Jul 3, 2013 at 5:02 PM, Julien D'ascenzio
julien.dascen...@paratronic.fr wrote:
When I use xusb with my product I have this message:
Reading Extended Compat ID OS Feature Descriptor (wIndex = 0x0004):
28 00 00 00 00 01 04 00 01 00 00 00 00 00 00 00
(...
On Thu, Jul 4, 2013 at 5:44 AM, Pete Batard p...@akeo.ie wrote:
If I don't do it today, it'll never happen, so here goes for review.
Looks good to me. Thanks.
--
Xiaofan
--
This SF.net email is sponsored by Windows:
On Wed, Jul 3, 2013 at 8:17 PM, Julien D'ascenzio
julien.dascen...@paratronic.fr wrote:
Ok thanks it's seems to be a windows strangeness :
'for Interface requests, the WinUSB DLL forces the low byte of wIndex
to the interface number' - Is that I have observed
I believe this is the case.
On Tue, Jul 2, 2013 at 1:32 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Tue, Jul 2, 2013 at 11:44 AM, Xiaofan Chen xiaof...@gmail.com wrote:
Sorry for the false alarm. It seems to do with using WinZIP
to un-archive the tar.bz2 file. Using MSys utility sorted out
the issue. Normally I am
On Mon, Jul 1, 2013 at 7:14 PM, Hans de Goede hdego...@redhat.com wrote:
You can find 1.0.16-rc2 docs including all the new API-s here:
http://people.fedoraproject.org/~jwrdegoede/libusb-reference/
One issue here:
http://people.fedoraproject.org/~jwrdegoede/libusb-reference/group__hotplug.html
On Mon, Jul 1, 2013 at 7:14 PM, Hans de Goede hdego...@redhat.com wrote:
You can download the 1.0.16-rc2 tarbal here:
http://downloads.sourceforge.net/libusbx/libusbx-1.0.16-rc2.tar.bz2
Please give it a thorough testing, and report any issues you
find.
It seems to fail to build under
On Sun, Jun 30, 2013 at 7:45 AM, Pete Batard p...@akeo.ie wrote:
https://github.com/libusbx/libusbx/commit/7b893cc7cee185c0bf771166ca61a05b32800556
should now fix the cywgin issue, as well as sort our gettimeofday()
usage for all the Windows compilers. It also includes the missing %s
reported
On Sun, Jun 30, 2013 at 4:28 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Sun, Jun 30, 2013 at 7:45 AM, Pete Batard p...@akeo.ie wrote:
Once more, given the amount of changes that have been pushed since RC1,
I would strongly suggest that we declare RC2 and push the 1.0.16
milestone (due
On Wed, Jun 26, 2013 at 11:22 PM, Hans de Goede hdego...@redhat.com wrote:
Thanks, that explains what is going on. I've just pushed 2 commits
to fix this. I would appreciate it if you could first run with only
the first commit applied:
core: Only do hotplug cleanup for hotplug capable backends
On Thu, Jun 27, 2013 at 11:15 PM, Hans de Goede hdego...@redhat.com wrote:
On 06/27/2013 03:49 PM, Toby Gray wrote:
This is a slightly reworked version of my previous logging patches.
I've improved the commit message for the first patch and made the
changes suggested by Hans de Goede
On Fri, Jun 28, 2013 at 2:33 AM, Hans de Goede hdego...@redhat.com wrote:
You're right, and I'm sorry. I guess I'm to much of a rero person sometimes.
Although win32 is far from my specialty I think the attach patch should fix
it. Any chance you could give it a try?
Even though it does not
On Thu, Jun 20, 2013 at 10:06 PM, Hans de Goede hdego...@redhat.com wrote:
I'm very happy to announce libusbx-1.0.16-rc1, highlights:
You can download the 1.0.16-rc1 tarbal here:
http://downloads.sourceforge.net/libusbx/libusbx-1.0.16-rc1.tar.bz2
Please give it a thorough testing, and report
On Sat, Jun 22, 2013 at 9:47 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Thu, Jun 20, 2013 at 10:06 PM, Hans de Goede hdego...@redhat.com wrote:
I'm very happy to announce libusbx-1.0.16-rc1, highlights:
You can download the 1.0.16-rc1 tarbal here:
http://downloads.sourceforge.net/libusbx
On Fri, Jun 14, 2013 at 4:08 PM, Hans de Goede hdego...@redhat.com wrote:
Hmm, as Nathan has already pointed out this is caused by pthread_create
failing. I think you may be running out of resources and/or hitting
a ulimit.
This may also be related to the udev fd not being non-blocking issue
On Fri, Jun 14, 2013 at 6:38 PM, Belkhiria Hamza Yazid
yoshipepper...@gmail.com wrote:
I realized a driverless application for HID communication based on HIDAPI
using th built in HID windows driver,
I am looking for a driverless solution for HID communication based on
Libusbx,
Is it possible
On Fri, Jun 14, 2013 at 5:59 PM, Hans de Goede hdego...@redhat.com wrote:
Hmm, ok, error 11 is EAGAIN, so indeed you're running out of some resource.
Can you give the attached patch a try please ?
Great. Your patch fixed the issues I have under Ubuntu Linux.
--
Xiaofan
On Thu, Jun 13, 2013 at 9:20 PM, Toby Gray toby.g...@realvnc.com wrote:
On 13/06/13 14:07, Hans de Goede wrote:
Hi,
On 06/13/2013 02:41 PM, Xiaofan Chen wrote:
stress test failed with the latest git tree.
1.0.15 release works fine.
mcuee@ubuntu1304vm:~/Desktop/build/libusbx$ ./tests/stress
On Thu, Jun 13, 2013 at 9:57 PM, Xiaofan Chen xiaof...@gmail.com wrote:
The error seems to be related to udev.
libusbx: error [linux_udev_start_event_monitor] could not create linux
hotplug event thread
libusbx: error [op_init] error starting hotplug event monitor
Failed to init libusb: -99
On Thu, Jun 13, 2013 at 10:02 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Thu, Jun 13, 2013 at 9:57 PM, Xiaofan Chen xiaof...@gmail.com wrote:
The error seems to be related to udev.
libusbx: error [linux_udev_start_event_monitor] could not create linux
hotplug event thread
libusbx: error
On Tue, Jun 11, 2013 at 5:58 AM, j...@serialtek.com wrote:
Thanks for the response. For some reason, usbview refuses to execute
on this system -- just spins the hourglass for a few seconds and then
nothing happens.
Nothing identifiable in the task manager's application list, nothing in the
On Fri, Jun 7, 2013 at 2:37 AM, Ludovic Rousseau
ludovic.rouss...@gmail.com wrote:
2013/6/6 Hans de Goede hdego...@redhat.com:
I've merged the pull request into master. Ludovic, this should fix your
problem, please test.
Problem fixed.
Great. Now the problem with stress test program under
On Sat, Jun 8, 2013 at 7:08 AM, j...@serialtek.com wrote:
We have an Asus motherboard with ASMedia xHCI USB 3.0 controller and have
tested driver versions 1.14.3.0 (latest Asus version from 2011) and 1.16.4.0
(latest web version we could find, 11/8/2012) and it has the weird behavior
on
On Tue, Jun 4, 2013 at 8:26 AM, Pete Batard p...@akeo.ie wrote:
On 2013.06.03 08:33, Hans de Goede wrote:
With this all said and done can we please have a decision (I guess
we vote?) on which one it is going to be ?
I vote blank.
If the .pc and libraries are stuck to -1.0, I'm going to have
On Tue, May 28, 2013 at 6:25 PM, Hans de Goede hdego...@redhat.com wrote:
This patch adds the much requested libusb_strerror() function, taking into
account all issues people raised wrt previous attempts.
Criteria / Decisions underlying this implementation:
-Must support translated messages
On Wed, May 29, 2013 at 8:18 PM, Ludovic Rousseau
ludovic.rouss...@gmail.com wrote:
2013/5/29 Hans de Goede hdego...@redhat.com:
Nope, a libusb_device is just a software struct representing the info
we could get from the OS about the device without actually opening
it, or talking to the
On Fri, May 17, 2013 at 4:47 AM, Hans de Goede hdego...@redhat.com wrote:
Hi all,
With some help from Pete, Xiaofan as well as Nathan, I have been working on
integrating the libusb hp API work done by Nathan for 1.0.16 on top of
libusbx.
We're planning to push these changes to libusbx
On Fri, May 17, 2013 at 4:47 AM, Hans de Goede hdego...@redhat.com wrote:
With some help from Pete, Xiaofan as well as Nathan, I have been working on
integrating the libusb hp API work done by Nathan for 1.0.16 on top of
libusbx.
We're planning to push these changes to libusbx master by the
On Thu, Apr 18, 2013 at 8:52 PM, NicoBats sl1200...@gmail.com 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
On Tue, Apr 16, 2013 at 8:00 PM, nico sl1200...@gmail.com 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]
On Tue, Apr 16, 2013 at 7:48 AM, Pete Batard p...@akeo.ie wrote:
On 2013.04.15 11:33, Toby Gray wrote:
However I
don't want to upload pre-built WinCE binaries without a copy of the LGPL
in the zip. Are you happy for me to continue to include COPYING in the
WinCE zips that I upload?
On Tue, Apr 16, 2013 at 12:29 AM, Daniel Goertzen
daniel.goert...@gmail.com wrote:
Hello, I am struggling with libusbx on cygwin under Windows 8. When I
configure and V=1 make I get the failed build output below. It looks
like a pthread linkage issue and I normally know how to deal with that,
On Sat, Apr 13, 2013 at 2:43 PM, nico sl1200...@gmail.com 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
On Thu, Apr 11, 2013 at 9:30 PM, nico sl1200...@gmail.com 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
On Fri, Apr 12, 2013 at 7:27 AM, Pete Batard p...@akeo.ie wrote:
If that's the case, then you may want to check 3 years of libusb mailing
list archives as well as one year of libusbx, because this topic has
probably been discussed about once every 3 months on each list.
I think the plan on
On Tue, Apr 9, 2013 at 5:54 AM, Pete Batard p...@akeo.ie wrote:
On 2013.04.08 19:12, Tim Roberts wrote:
Xiaofan Chen wrote:
Somehow I got a strange warning under Windows 8 x64. The device
is a USB composite device (Amontec JTAGkey-2), both interface
use the WinUSB driver installed using Zadig
On Tue, Apr 9, 2013 at 10:46 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Tue, Apr 9, 2013 at 5:54 AM, Pete Batard p...@akeo.ie wrote:
With this being said, I ran a test on Windows 8 against an FTDI based
composite device (Olimex JTAG), and did not see the issue reported by
Xiaofan.
Yes
1 - 100 of 398 matches
Mail list logo
