On Wed, Aug 6, 2014 at 9:08 AM, Bob Tausworthe 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 thread
> or do I n
On Wed, Jul 30, 2014 at 5:28 AM, Bob Tausworthe wrote:
> Sorry to trouble you but I've exhausted other options. We are developing a
> composite HID/debug interace device and are using libusb 1.0 under 32 bit
> Cygwin to access the debug interface portion. Everything is working fine on
> Windows 7
On Wed, Feb 12, 2014 at 1:13 PM, Nothing 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 Wed, Feb 12, 2014 at 10:09 AM, Nothing wrote:
> I use libusb1.0.18 but libusb_has_capability () return false ?
>
> the attach file is the source file of linux please give me some help
> ,thanks very much
>
Please do not attach libusb binaries. They are totally useless for
others.
Please te
On Sat, Feb 8, 2014 at 1:13 AM, hgs16 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,...) (write) to
> t
On Tue, Jan 28, 2014 at 3:34 AM, Spiro Trikaliotis
wrote:
> Hello,
>
> * On Mon, Jan 27, 2014 at 01:15:04PM +0800 Xiaofan Chen wrote:
>
>> * IF YOU ARE AN EXISTING LIBUSB USER:
> [...]
>> - The mailing list remains at
>>libusbx-devel@lists.sourceforge.
On Sun, Jan 12, 2014 at 10:22 AM, Xiaofan Chen 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 "derefer
On Thu, Jan 9, 2014 at 9:50 AM, Pete Batard wrote:
> All,
>
> It is my great pleasure to announce libusb-1.0.18 RC1, which marks the
> long awaited merge-back of libusbx with libusb!
> ...
> To check the RC, you are invited to go http://libusb.info, and use the
> Download menu, which should give y
On Fri, Jan 10, 2014 at 3:19 PM, Pradeepa Senanayake
wrote:
> So in that case, with this new release which I got through
> http://libusb.info/ what are the compatible drivers?
>
>
https://github.com/libusb/libusb/wiki/Windows
--
Xiaofan
On Fri, Jan 10, 2014 at 3:12 PM, Xiaofan Chen wrote:
> On Fri, Jan 10, 2014 at 2:17 PM, Pradeepa Senanayake
> 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 u
On Fri, Jan 10, 2014 at 2:17 PM, Pradeepa Senanayake
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 open the device an
On Wed, Dec 25, 2013 at 10:57 AM, Nothing wrote:
>
>
> it still have this error
>
How did you build libusbx 1.0.17?
--
Xiaofan
--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations
On Wed, Dec 25, 2013 at 12:06 AM, Nothing 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 this platform
On Tue, Nov 26, 2013 at 12:38 PM, Nothing 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 posts may be rejec
On Mon, Nov 25, 2013 at 10:42 PM, Nothing 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 hotplug in and out fu
On Tue, Nov 26, 2013 at 4:41 AM, Liang Zhu 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 Sat, Nov 23, 2013 at 3:38 AM, Kustaa Nyholm
wrote:
> Hi,
>
> this really OT for this list but I hope some one can
> help me all the same.
>
> I'm writing a HIDAPI like interface but with Java
> and JNA only.
>
> I can now enumerate the devices but when I try to
> open my test HID device (a gene
On Tue, Nov 12, 2013 at 1:02 PM, Kustaa Nyholm
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 wrote:
> On Sat, Sep 21, 2013 at 1:42 PM, Kano 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 be
On Sat, Sep 21, 2013 at 1:42 PM, Kano 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 be associated with multiple interface.
> libusb_get_device_list
> libusb_get_device_descriptor
On Sat, Sep 21, 2013 at 7:21 AM, Kano 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 special rules
On Sat, Sep 21, 2013 at 10:26 AM, Kano 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 Cairnsmore1_\(Interfac
On Tue, Sep 17, 2013 at 2:45 PM, Ramon Zambelli
wrote:
>> Also note that there exists limitations with regards to using WinUSB when
>> accessing interfaces using LIBUSB_RECIPIENT_INTERFACE
>> See
>> https://github.com/libusbx/libusbx/wiki/Windows-Backend#wiki-Known_Restrictions
>
> From the linkj
On Tue, Sep 17, 2013 at 2:09 PM, Gary Carlson
wrote:
> automake: warning: possible forward-incompatibility.
> automake: At least a source file is in a subdirectory, but the
> 'subdir-objects'
> automake: automake option hasn't been enabled. For now, the corresponding
> output
> automake: object f
On Tue, Sep 17, 2013 at 6:08 AM, Ramon Zambelli
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 interfac
On Sun, Sep 15, 2013 at 8:08 PM, Ramon Zambelli
wrote:
> I have a device which used WCID to install WinUSB drivers. The driver
> installs automatically as expected, but when I try to open the device
> using libusbx 1.17 I get error -12 (ERROR_NOT_SUPPORTED). I'm using
> windows 8.
> Using zadig I
On Fri, Sep 6, 2013 at 10:52 PM, Hans de Goede wrote:
> Signed-off-by: Hans de Goede
> ---
> 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 | 4 +---
> libusb/os/openbsd
On Sat, Sep 7, 2013 at 11:36 PM, Alan Stern 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 usbfs API directly, r
On Fri, Sep 6, 2013 at 6:58 PM, Hans de Goede 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
> c
On Thu, Sep 5, 2013 at 3:26 AM, Hans de Goede wrote:
> Hi,
>
> As discussed in much detail here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1003193
>
> Calling libusb_exit from atexit from libusb-compat-0.1.5 causes
> some apps to break.
>
> The app in question is the scanimage app from sane-ba
On Mon, Sep 2, 2013 at 7:48 PM, Gisle Vanem wrote:
> BTW. How come SF's Mailman doesn't send me copies of my own
> messages even though I've told it so? I've checked the settings at
> https://lists.sourceforge.net/lists/options/libusbx-devel
> and see that "Receive your own posts to the list?
On Sat, Aug 31, 2013 at 12:21 AM, Gisle Vanem 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: '=' : conversion from
On Fri, Aug 30, 2013 at 4:14 PM, Xiaofan Chen wrote:
> On Wed, Aug 28, 2013 at 5:35 PM, Hans de Goede 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
On Fri, Aug 30, 2013 at 8:47 PM, Xiaofan Chen wrote:
> On Fri, Aug 30, 2013 at 4:14 PM, Xiaofan Chen wrote:
>> On Wed, Aug 28, 2013 at 5:35 PM, Hans de Goede wrote:
>>> I'm very happy to announce libusbx-1.0.17-rc1.
>>>
>>> You can down
On Fri, Aug 30, 2013 at 4:14 PM, Xiaofan Chen wrote:
> On Wed, Aug 28, 2013 at 5:35 PM, Hans de Goede 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
On Wed, Aug 28, 2013 at 5:35 PM, Hans de Goede 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 you find.
I di
On Sat, Aug 24, 2013 at 10:30 AM, Juan Lang 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 USB_NODE_CONNECTION_
On Mon, Aug 26, 2013 at 7:32 PM, Martin Pieuchot 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 branch", instead we
On Fri, Aug 23, 2013 at 9:36 PM, Xiaofan Chen 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.
On Sat, Aug 24, 2013 at 12:44 AM, Juan Lang wrote:
> 2013/8/22 Xiaofan Chen
>> Again I agree with you. On the other hand, I think it is still good
>> if Juan can come out a version for review. I do not mind review and
>> carry out some testing myself.
>
> Thanks Xia
On Fri, Aug 23, 2013 at 9:32 PM, Xiaofan Chen wrote:
> On Fri, Aug 23, 2013 at 9:02 PM, Xiaofan Chen wrote:
>> On Thu, Aug 22, 2013 at 10:50 PM, Hans de Goede wrote:
>>> On 08/22/2013 03:30 AM, Xiaofan Chen wrote:
>>>> For OpenBSD and NetBSD, I can carry out s
On Fri, Aug 23, 2013 at 9:02 PM, Xiaofan Chen wrote:
> On Thu, Aug 22, 2013 at 10:50 PM, Hans de Goede 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 tes
On Fri, Aug 23, 2013 at 9:02 PM, Xiaofan Chen wrote:
> On Thu, Aug 22, 2013 at 10:50 PM, Hans de Goede 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 tes
On Thu, Aug 22, 2013 at 10:50 PM, Hans de Goede 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
On Wed, Aug 14, 2013 at 7:52 AM, Pete Batard 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.
On Fri, Aug 23, 2013 at 9:30 AM, Pete Batard 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 but have so
On Fri, Aug 23, 2013 at 9:51 AM, Pete Batard 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
>
On Fri, Aug 23, 2013 at 2:29 AM, Juan Lang wrote:
> 2013/8/21 Xiaofan Chen
>>
>> 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
On Thu, Aug 22, 2013 at 10:51 AM, Xiaofan Chen wrote:
> On Thu, Aug 22, 2013 at 10:37 AM, Juan Lang wrote:
>>> Have your reported the bug to the vendor and have you try to
>>> upgrade your driver to the latest version?
>>
>>
>> No, and yes. I've seen t
On Thu, Aug 22, 2013 at 10:37 AM, Juan Lang wrote:
>> Have your reported the bug to the vendor and have you try to
>> upgrade your driver to the latest version?
>
>
> No, and yes. I've seen this across a variety of hardware:
>
>> You mentioned that you have problem with a TI controller and
>> an I
On Tue, Aug 20, 2013 at 9:15 PM, Toby Gray 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 maintainer of libusb so
On Wed, Aug 21, 2013 at 10:48 PM, Hans de Goede wrote:
>> then I'll give people
>> until Thursday evening to test things from git-master and I'll
>> release 1.0.17-rc1 on Friday.
>
> Given the nature of the patches (ie the netbsd openbsd split), I think it
> will be better to delay the rc1 release
On Thu, Aug 22, 2013 at 6:54 AM, Juan Lang wrote:
> Hi folks,
> this is a followup to my earlier query about USB 3 ports failing on Windows
> 7. I've confirmed that the failures I see are due to bugs in the USB 3 port
> drivers, which don't support the
> IOCTL_USB_GET_NODE_CONNECTION_INFORMATION_E
On Mon, Aug 19, 2013 at 11:34 PM, Hans de Goede 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 release a while
On Fri, Aug 16, 2013 at 4:51 PM, Hans de Goede 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
>>
On Fri, Aug 16, 2013 at 2:10 PM, wrote:
> If so sorry.
> The system is winxp and win7
>
In that case, you may want to read the following Microsoft KB.
http://support.microsoft.com/kb/823732
Or search the internet for more options.
Again this is off topic.
--
Xiaofan
--
On Mon, Aug 12, 2013 at 10:27 AM, Xiaofan Chen wrote:
> FYI.
>
> On Mon, Aug 12, 2013 at 1:18 AM, Travis wrote:
>> Greetings,
>>
>> libusbK v3.0.6.0 has just been released:
>> https://sourceforge.net/projects/libusbk/files/libusbK-release/3.0.6.0/
>>
On Wed, Aug 14, 2013 at 10:05 PM, Hans de Goede wrote:
> From: Daniel Berrange
>
> 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
the ticket #130 for libusb-compat-0.
On Fri, Aug 16, 2013 at 2:24 AM, Tim Roberts wrote:
> Xiaofan Chen wrote:
>> Secondly how does usbccgp.sys rewrites the configuration
>> descriptors?
>
> It eliminates everything related to the interfaces that you did not
> claim in your INF. If you claimed MI_03,
On Thu, Aug 15, 2013 at 11:08 PM, 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 nothing to do w
On Thu, Aug 15, 2013 at 12:45 AM, Tim Roberts 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
&g
On Wed, Aug 14, 2013 at 2:46 PM, Jan Becvar 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 in my us
On Wed, Aug 14, 2013 at 3:23 PM, luis morales
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 achived the .inf file. The firs
On Wed, Aug 14, 2013 at 3:48 AM, Jan Becvar 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 take time. An
On Wed, Aug 14, 2013 at 2:26 AM, Pete Batard 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 so, as
On Wed, Aug 14, 2013 at 12:23 AM, Tim Roberts wrote:
>
> Xiaofan Chen wrote:
> > I think there is a way to hack the inf-file generated by
> > Zadig to install WinUSB driver for each interface.
> >
> > Interface 0 --> MI_00
> > Interface 1 --> MI_01
&g
On Tue, Aug 13, 2013 at 10:40 PM, Jan Becvar 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 Interf
On Tue, Aug 13, 2013 at 6:15 PM, Jan Becvar 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
On Tue, Aug 13, 2013 at 4:36 PM, Jan Becvar 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() error with
On Tue, Aug 13, 2013 at 9:53 PM, Xiaofan Chen wrote:
> On Tue, Aug 13, 2013 at 6:15 PM, Jan Becvar 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.aspx
&
On Tue, Aug 13, 2013 at 6:15 PM, Jan Becvar 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
On Tue, Aug 13, 2013 at 4:36 PM, Jan Becvar 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() error with
On Tue, Aug 13, 2013 at 4:45 AM, Pete Batard wrote:
> On 2013.08.12 14:15, Xiaofan Chen wrote:
>> 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\w
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
-
On Mon, Aug 12, 2013 at 8:08 PM, Toby Gray 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 have.
--
Xiaofan
---
On Fri, Aug 9, 2013 at 6:51 PM, Toby Gray 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 more basic than the
FYI.
On Mon, Aug 12, 2013 at 1:18 AM, Travis 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 case as Google
On Mon, Aug 5, 2013 at 7:39 AM, Pete Batard 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 cache
On Sun, Aug 4, 2013 at 9:08 AM, Pete Batard wrote:
> On 2013.08.04 00:51, Alan Stern wrote:
>> Out of curiosity, what data do you need to request from the parent hub?
>
> Now that I've looked a bit through old e-mails, it seems that these are
> config descriptors, coming from a Windows
> IOCTL_USB
To libusbx mailing list as well.
-- Forwarded message --
From: Paul Fertser
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
With these amendments (borrowed from the
On Fri, Aug 2, 2013 at 6:02 PM, Hans de Goede 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 NetBSD then I
On Tue, Jul 30, 2013 at 11:38 PM, Hans de Goede 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 Pete
On Wed, Jul 10, 2013 at 9:28 AM, Xiaofan Chen wrote:
> On Thu, Jul 4, 2013 at 5:14 PM, Xiaofan Chen wrote:
>> On Wed, Jul 3, 2013 at 3:29 AM, Sean McBride wrote:
>>> On Tue, 2 Jul 2013 23:18:12 +0400, Paul Fertser said:
>>>>What about documenting this in s
On Wed, Jul 31, 2013 at 4:40 PM, Hans de Goede 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
>>> https://github.com/libusbx/libusbx/issues/123#issuecomment-21789151?
On Wed, Jul 31, 2013 at 5:25 AM, Pete Batard 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 switc
On Mon, Jul 29, 2013 at 9:05 AM, Pete Batard wrote:
> On 2013.07.29 00:15, James Ohr wrote:
> > [ 0.029002] [0001271c] libusbx: debug [get_api_type] driver(s): HidUsb
> > [ 0.029002] [0001271c] libusbx: debug [get_api_type] lower filter
> > driver(s): LUsbFilt
> > [ 0.029002] [0001271c] libusb
On Mon, Jul 29, 2013 at 7:15 AM, James Ohr wrote:
> I connect a camera and an MP3 player to a Windows 7 64-bit system to test
> with. When I run this I get a return code of a -5 (LIBUSB_ERROR_NOT_FOUND).
> I turn on logging and receive errors that show that
> [winusbx_claim_interface] is not able
On Sat, Jul 27, 2013 at 10:45 AM, Xiaofan Chen wrote:
> On Sat, Jul 27, 2013 at 12:04 AM, jakubon2 wrote:
>> Or alternatively,
>>
>> does it mean I should revert in Git to the version of old /libusb/ (=not
>> /libusbx/)?
>>
>
> Since you do not need hotpl
On Thu, Jul 25, 2013 at 4:04 PM, Egli, Samuel 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 current one (v2013-07).
On Wed, Jul 24, 2013 at 7:40 PM, jakubon2 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
> CC='arm-xilinx-linux-gnueabi-gcc'
> CROSS_COMPILE=a
On Thu, Jul 25, 2013 at 12:52 AM, Juan Lang 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 problem on an HP
On Fri, Jul 12, 2013 at 3:14 PM, Hans de Goede 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 the index page.
On Fri, Jul 12, 2013 at 8:34 AM, Xiaofan Chen wrote:
> On Fri, Jul 12, 2013 at 2:34 AM, Jens Gutsche wrote:
>> Hi,
>>
>> i have seen a new version on http://www.libusb.org/wiki but i cannot
>> configure it.
>>
>> Here is the console output:
>>
>>
On Fri, Jul 12, 2013 at 8:46 AM, Nathan Hjelm wrote:
> On Jul 11, 2013, at 6:34 PM, Xiaofan Chen wrote:
>> The netlink support is not well tested as far as I know.
>
> It works but it looks like in this case the headers are not usable. We really
> should stress that netlink sup
On Fri, Jul 12, 2013 at 2:34 AM, Jens Gutsche wrote:
> Hi,
>
> i have seen a new version on http://www.libusb.org/wiki but i cannot
> configure it.
>
> Here is the console output:
>
> bash-3.2$ ./configure --prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin
> --libdir=/usr/lib --disable-static --e
On Wed, Jul 10, 2013 at 1:50 PM, igx deepak 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:
http://libu
On Tue, Jul 9, 2013 at 9:51 PM, Hans de Goede wrote:
> Headsup: unless there are any objections I plan to release 1.0.16 coming
> Thursday.
>
Great. 1.0.16 is an important milestone.
--
Xiaofan
--
See everything from
On Thu, Jul 4, 2013 at 5:14 PM, Xiaofan Chen wrote:
> On Wed, Jul 3, 2013 at 3:29 AM, Sean McBride 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?
>
On Sun, Jul 7, 2013 at 6:21 PM, Xiaofan Chen wrote:
> On Sun, Jul 7, 2013 at 9:10 AM, Xiaofan Chen wrote:
>> On Sat, Jul 6, 2013 at 3:15 PM, Hans de Goede wrote:
>>> I'm very happy to announce libusbx-1.0.16-rc3.
>>
>> Just carried out some quick tests unde
On Sun, Jul 7, 2013 at 9:10 AM, Xiaofan Chen wrote:
> On Sat, Jul 6, 2013 at 3:15 PM, Hans de Goede 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.
>
C
1 - 100 of 678 matches
Mail list logo
