With the release of libusbx-1.0.18 and libusb-1.0.18, the issue can probably be
closed. Or maybe we have to migrate all the issues to github libusb
organization first.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/123#issuecomment-34283279--
ST has since updated the driver to support Windows 8. I just tried
libusbx-1.0.18 under Windows 8.1 x64 and it works fine with ST's updated
driver. So I will close this issue.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/119#issuecomment-333171
Closed #119.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/119--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing Century
Close with
https://github.com/libusbx/libusbx/commit/5bbbfc98bd309ab9425a6fb96b77bde9a5b244e6
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/143#issuecomment-33316919--
Ce
Closed #143.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/143--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing Century
Closed #146.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/146--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing Century
@Chirs: Nice. Where do you keep you code?
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/9#issuecomment-32585532--
CenturyLink Cloud: The Leader in Enterprise Cloud Service
Ref to Tim's question to OSR NTDEV list and the answer from Microsoft.
http://www.osronline.com/showthread.cfm?link=251465
There is no new WinUSB coinstaller in the 8.1 kit to install downlevel. nothing
in there is tied to
strictly to umdf, so that is not the reason there is no downlevel in
In that case, this can not be fixed. Maybe a document fix is good to have.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/155#issuecomment-30213972--
Sponsored by Intel(R)
Ref: https://github.com/libusbx/libusbx/issues/4
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/163#issuecomment-30213816--
Sponsored by Intel(R) XDK
Develop, test and displ
I tend to agree that a lack of WinUSB isoc support should prevent adding the
libusbK isoc support.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/164#issuecomment-30213434--
Looks good to me.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/152#issuecomment-25858405--
October Webinars: Code for Performance
Free Intel webinars can help you accelerat
Same warning under MinGW-w64 gcc 4.8.1.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/149#issuecomment-25154654--
October Webinars: Code for Performance
Free Intel webinar
Under latest MinGW.org gcc (4.8.1), there is a warning for ezusb.c
ezusb.c: In function 'ezusb_load_ram':
ezusb.c:719:6: warning: 'ret' may be used uninitialized in this function [-Wmayb
e-uninitialized]
int ret;
---
Reply to this email directly or view it on GitHub:
https://github.com
Just want to copy the comments on top of enum.c here.
The enumeration process goes like this:
(1) Enumerate Host Controllers and Root Hubs
EnumerateHostControllers()
EnumerateHostController()
Host controllers currently have symbolic link names of the form HCDx,
wher
This is just a token issue to be closed when we release.
Required as closing all the other issues will close the milestone.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/145--
This is just a token issue to be closed when we release.
Required as closing all the other issues will close the milestone.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/146--
But if this is not ready, we can delay this.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/144#issuecomment-24908132--
LIMITED TIME SALE - Full Year of Microsoft Training
Linux and Mac OS X first.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/144--
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorial
* USB 3.0 Bulk Stream Support (Linux and Mac OS X)
* Bug fix
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/143--
LIMITED TIME SALE - Full Year of Microsoft Training For Ju
In the current libusbx implementation, the topology information is important
since it is part of the topology API.
BTW, have you been able to update your xHCI driver to see if your original
issue goes away? That is a better solution IMHO.
---
Reply to this email directly or view it on GitHub:
I do not understand your comment. libusbx and libusb are the same in this
aspect. What is the real issue you are facing?
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/3#issuecomment-24861275
I do not have a test setup to effectively testing this patch. We also know that
this is a work around for some 3rd party xhci controller driver/firmware bugs
where the new driver may already fix the issues.
Ref:
http://libusbx.1081486.n5.nabble.com/Libusbx-devel-Reading-device-descriptor-and-co
A few other things.
1) Warning message
$ ./examples/listdevs.exe
libusbx: warning [force_hcd_device_descriptor] could not infer VID/PID of HCD hu
b from '\\.\USB#VID_413C&PID_2513#6&2DA13301&0&2'
libusbx: warning [force_hcd_device_descriptor] could not infer VID/PID of HCD hu
b from '\\.\USB#VID_
I tried your tree, it caused stress test to fail.
$ ./tests/stress.exe
Failed to open null handle: 2
Interesting thing is that if I set LIBUSB_DEUG=4 and then run
"./tests/stress.exe -v" it will pass the tests. In that case, it will keep
printing an error message.
libusbx: error [windows_hotplu
Since this issue will only affect very few users and there is a workaround (to
use Zadig), I think this is not a high priority issue to debug and fix.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/140#issuecomment-24635001---
Ref:
http://libusbx.1081486.n5.nabble.com/Libusbx-devel-RFC-0-2-Add-support-for-USB-3-bulk-streams-td1911i20.html#a1937
Under Windows, libusbx fails to access WCID interface of a USB composite device
when using the Windows 7/8 built-in WinUSB driver (with system winusb.inf).
When using Zadig to
More discussions here:
http://libusbx.1081486.n5.nabble.com/Libusbx-devel-libusbx-android-support-132-td1779.html
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/132#issuecomment-23068473
-
One potential alternative is to use WinUSB driver to get the information
instead of the IOCTLs.
Ref:
http://libusbx.1081486.n5.nabble.com/Libusbx-devel-Reading-device-descriptor-and-config-descriptor-from-WinUsb-td1806.html
---
Reply to this email directly or view it on GitHub:
https://github.c
Ref:
http://libusbx.1081486.n5.nabble.com/Libusbx-devel-Accessing-composite-devices-using-interface-association-td1726.html
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/135
BTW, I think it is perfectly okay for you to mention that you only test VS2012.
I do not use VS much myself. And I think we may want to drop MSVC 6.0 support
since I think it is too old to support. And even VS2005 is quite old but
probably it is also for VS2008 users.
---
Reply to this email di
Reopened #129.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/129
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designe
I think you forget to update libusb_dll_2010.vcxproj.filters as well.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/129#issuecomment-22533621
--
Get 100% visibility into
BTW, the VS2012 files are good in this aspect.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/129#issuecomment-22491895
--
Get 100% visibility into Java/.NET code with AppD
Yes you are right. This is still in libusbx.git. The project file needs to be
updated.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/129#issuecomment-22489846
--
Get 100%
Take note Peter Stuge still owns libusb.org domain name. So he can changes back
the libusb.org if he wants to do that.
http://whois.net/whois/libusb.org
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/123#issuecomment-21834506
-
Closed #124.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/124
--
Get your SQL database under version control now!
Version control is standard for application code, but da
As per Ondrej, the fix is good.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/124#issuecomment-21763496
--
Get your SQL database under version control now!
Version control
Under Mac OS X Homebrew and automake 1.14.
mymacmini:libusbx xiaofanc$ ./autogen.sh
glibtoolize: putting auxiliary files in `.'.
glibtoolize: copying file `./ltmain.sh'
glibtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
glibtoolize: copying file `m4/libtool.m4'
glibtoolize: copying fi
The following fix is good to have to silent automake 1.14 warnings.
https://github.com/hjelmn/libusbx/commit/441185930942e35c418c07cf55449197a71987f6
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/125
--
So I will open the issue again. Then I will close the issue if the test code
works.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/124#issuecomment-21698149
--
See everyth
Reopened #124.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/124
--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with applica
>From config.log of user mav.
configure:12061: checking linux/netlink.h usability
configure:12061: /home/mav/nios2/bin/nios2-linux-gcc -c -g -O2 conftest.c >&5
In file included from conftest.c:58:
/home/mav/nios2/bin/../lib/gcc/nios2-linux-uclibc/3.4.6/../../../../nios2-linux-uclibc/sys-inclu
>From the config.log from user Ondrej.
...
configure:12030: checking linux/netlink.h usability
configure:12030: arm-xilinx-linux-gnueabi-gcc -c -g -O2 conftest.c >&5
In file included from conftest.c:58:0:
/opt/Xilinx/14.3/ISE_DS/EDK/gnu/arm/lin64/bin/../arm-xilinx-linux-gnueabi/libc/usr/incl
BTW, I tested desktop Linux Ubuntu 12.04 x86 and --disable-udev works fine
there.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/124#issuecomment-21658699
--
See everythin
Ref:
http://libusb.6.n5.nabble.com/libusb-1-0-16-rc10-without-udev-td5711991.html
The problem seems to be that netlink headers does not seem to work for many
embedded Linux distros and libusbx treat that as an error and abort the build
process. Probably it should continue and disable hotplug fo
Ref:
http://libusbx.1081486.n5.nabble.com/Libusbx-devel-Possible-alignment-issues-with-struct-libusb-transfer-buffer-pointer-td1458.html
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/120
--
47 matches
Mail list logo
