Ref: http://sourceforge.net/apps/trac/libusbx/roadmap
I think 1.0.11 target is already quite aggressive.
For 1.0.12, I think we may need more details.
Milestone: v1.0.12
Due in 4 months (09/01/12)
[New features]
* OSX: add HID support
* Windows: libsub0.sys driver support
* Windows: libusbK.sys
On Fri, Apr 20, 2012 at 6:38 PM, Pete Batard p...@akeo.ie wrote:
On 2012.04.20 11:03, Xiaofan Chen wrote:
I will say OS X HID backend is a nice to have feature
but not absolutely necessary, could be in 1.0.13 or 2.0.
Actually, it was stated for 1.0.11 and I moved it to 1.0.12, as I don't
On Sat, Apr 21, 2012 at 8:32 AM, Jose Pablo josepablo.cas...@gmail.com wrote:
Hi everybody
Can you change the name of this files?
From: To:
libusb.h libusbx.h
libusb-1.0.a libusbx-1.0.a
libusb-1.0.la
On Mon, Apr 16, 2012 at 4:16 PM, Hans de Goede hdego...@redhat.com wrote:
http://www.libusb.org/report/12?sort=typeasc=1page=1
Peter has changed some component type in libusb.org.
So I have to change the report syntax again and now
it should work again.
On Tue, Apr 24, 2012 at 4:31 AM, Hans de Goede hdego...@redhat.com wrote:
Hi,
On 04/23/2012 07:31 PM, Garret Kelly wrote:
Then we should begin actively discussing this issue with the people
who it _is_ up to. Preferably who're going to be doing the distro
packaging, because they're going to
On Wed, May 2, 2012 at 1:35 PM, 付帅兵 fushuaib...@centerm.com.cn wrote:
I used libusbx which version is 1.0.10 for LINUX OS,
copy data from PC to U disk, sometimes the device disapeared for
special U disk.
I look for code and find the libusb_interrupt_or_bulk_transfer return
error which
is
On Thu, May 3, 2012 at 6:56 PM, Pete Batard p...@akeo.ie wrote:
On 2012.05.03 02:47, Xiaofan Chen wrote:
Also Tim's view on this topic in the OSR mailing list / forum.
http://www.osronline.com/showthread.cfm?link=223812
+++
One can also argue that this is a security measure. The USB spec
On Fri, May 4, 2012 at 8:47 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Thu, May 3, 2012 at 6:56 PM, Pete Batard p...@akeo.ie wrote:
The issue was that I thought Microsoft mandated the use of an arbitrary
wIndex with an interface recipient when reading the WCID properties,
and thus were
On Sun, May 6, 2012 at 11:55 AM, Xiaofan Chen xiaof...@gmail.com wrote:
This is what I have under OpenBSD and I think it looks fine.
Similar for NetBSD (6.0 Beta).
bash-4.2$ ./listdevs
[timestamp] [threadID] facility level [function call] message
On Sat, May 5, 2012 at 3:18 PM, Hans de Goede hdego...@redhat.com wrote:
libusbx is already calling pthread_setname_np() for the thread it creates.
But only for OS X I assume...
Sean, maybe it would be an idea for the os dependent code to print a
thread name + id when creating a thread and
On Mon, May 7, 2012 at 11:16 PM, Pete Batard p...@akeo.ie wrote:
On 2012.05.07 15:47, Pete Batard wrote:
On 2012.05.07 14:40, Xiaofan Chen wrote:
As per Matin (the author of the OpenBSD backend), you can
use the getthrid() syscall that returns a pid_t.
Great. I'll give it a try
On Tue, May 8, 2012 at 10:29 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Sat, May 5, 2012 at 3:18 PM, Hans de Goede hdego...@redhat.com wrote:
libusbx is already calling pthread_setname_np() for the
thread it creates.
But only for OS X I assume...
Sean, maybe it would be an idea
On Tue, May 8, 2012 at 6:08 PM, Pete Batard p...@akeo.ie wrote:
On 2012.05.08 01:10, Xiaofan Chen wrote:
A few warnings under NetBSD 6.0 Beta. Other than that, it
seems to work fine.
CC libusb_1_0_la-openbsd_usb.lo
os/openbsd_usb.c: In function '_sync_control_transfer':
os
On Tue, May 8, 2012 at 6:16 PM, Pete Batard p...@akeo.ie wrote:
On 2012.05.08 11:07, Xiaofan Chen wrote:
Martin's answer:
This is normal, you must use an OpenBSD -current in order
to have real threads enable, until 5.1 OpenBSD only has
userland threads.
OK. If possible, can you try
On Mon, May 14, 2012 at 7:56 PM, Pete Batard p...@akeo.ie wrote:
Moving on with the list of 1.0.12 items, the attached patch reinstates HID
support for Windows, as well as adds HID feature reports querying to xusb.
Great. I should be able to give this some tests, like Jan Axelson's
generic HID
On Mon, May 14, 2012 at 9:16 PM, Xiaofan Chen xiaof...@gmail.com wrote:
Somehow xusb now segfaults sometimes.
BTW, 1.0.11 release never segfaults.
mymacmini:examples xiaofanc$ ./xusb -d 04d8:fa2e
Using libusbx v1.0.11.10499
Opening device...
[timestamp] [threadID] facility level [function
On Mon, May 14, 2012 at 9:19 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Mon, May 14, 2012 at 9:16 PM, Xiaofan Chen xiaof...@gmail.com wrote:
Somehow xusb now segfaults sometimes.
BTW, 1.0.11 release never segfaults.
The default xusb is actually a wrapper. So I rebuild xusb with static
On Mon, May 14, 2012 at 7:50 PM, Pete Batard p...@akeo.ie wrote:
v2, that takes into account what was discussed previously (but still
provides get_parent).
Seems to work fine under Windows.
The difference between the first run and the 2nd run is that
I add an old full-speed USB Hub in between
On Mon, May 14, 2012 at 8:24 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Mon, May 14, 2012 at 7:56 PM, Pete Batard p...@akeo.ie wrote:
Moving on with the list of 1.0.12 items, the attached patch reinstates HID
support for Windows, as well as adds HID feature reports querying to xusb.
Great
On Mon, May 14, 2012 at 7:50 PM, Pete Batard p...@akeo.ie wrote:
v2, that takes into account what was discussed previously (but still
provides get_parent).
Obviously the two BSDs do not support this feature and I do not
see this is mentioned in your patch.
BTW, I have checked with Martin and
On Fri, May 18, 2012 at 8:27 AM, dan dw5...@gmail.com wrote:
after noon guys im trying to port the ubertooth over to windows and get it
working properly.
im running into a bit of a snag though.
gcc ubertooth-dump.c ubertooth.c -o ubertooth-dump -llibusb-1.0 -lbtbb
This does not seem to be
On Fri, May 18, 2012 at 11:02 PM, Pete Batard p...@akeo.ie wrote:
On 2012.05.18 15:23, dan wrote:
ok pete i tryed it again,
got a bit of a different message, but still failed.
http://pastebin.com/6utL3N9N
Also since you are using Cygwin which has its older libusb-1.0,
you may want to remove
On Tue, May 15, 2012 at 11:19 PM, Pete Batard p...@akeo.ie wrote:
On 2012.05.15 01:03, Pete Batard wrote:
Could be that we're
trying to access unref'd and restroyed parent devices on OS-X, hence the
seemingly random outcome.
Yup. Confirmed that some of the parents we're trying to access get
On Mon, May 14, 2012 at 10:54 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Mon, May 14, 2012 at 8:24 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Mon, May 14, 2012 at 7:56 PM, Pete Batard p...@akeo.ie wrote:
Moving on with the list of 1.0.12 items, the attached patch reinstates HID
support
On Wed, May 2, 2012 at 4:28 PM, Hans de Goede hdego...@redhat.com wrote:
Hi,
On 05/01/2012 10:29 PM, Pete Batard wrote:
On 2012.05.01 16:52, Uri Lublin wrote:
Only if old backend api is UNSUPPORTED.
This happens when a libusb driver (e.g. WinUSB) is installed
after a device has been
There is a warning, not so sure if it is really of importance or not.
The good thing is that ST-Link V2 uses Winusb.sys and libusbx
works out of the box, without the need to switch driver.
(ST-Link V1 uses USB Mass Storage driver).
C:\work\libusbx\libusbx-1.0.11-win\examples\bin32xusb.exe -d
On Mon, May 21, 2012 at 8:11 PM, Hans de Goede hdego...@redhat.com wrote:
The problem is that with usb device redirection we can have 1 device
already redirected, and then the user asks to redirect another device
to the virtual machine, so we install a driver for the other device,
and then
On Tue, May 22, 2012 at 5:11 PM, Peter Stuge pe...@stuge.se wrote:
Xiaofan Chen wrote:
I think the warning message is a bit miss-leading. If libusbx found
/, then it should probably warn against unrecognized device.
If Windows says that there is a 0:0 device when there is actually
On Tue, May 22, 2012 at 9:52 PM, g...@novadsp.com g...@novadsp.com wrote:
Agreed. However the complaint is not about my device - the VID/PID is
for something else. What I'm trying to establish is which slice in the
stack is sending the warning.
In that case, that is just a warning about
On Wed, May 23, 2012 at 6:25 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Wed, May 23, 2012 at 5:30 PM, Hans de Goede hdego...@redhat.com wrote:
Hi,
In the Fedora libusbx packages we ship example/*.c as part of the
development documentation. ATM we run this script on these files
because
On Thu, May 24, 2012 at 9:17 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Thu, May 24, 2012 at 9:12 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Thu, May 24, 2012 at 7:10 PM, Pete Batard p...@akeo.ie wrote:
Finally got around looking further at the Darwin issue. It looks like the
main
On Thu, May 24, 2012 at 7:11 PM, Pete Batard p...@akeo.ie wrote:
While I was at it, and since it's an open 1.0.12 item
(https://sourceforge.net/apps/trac/libusbx/ticket/1)...
Apart from one message that looked like info we want to carry out with debug
level info, most of the usbi_info() calls
On Fri, May 25, 2012 at 3:19 AM, g...@novadsp.com g...@novadsp.com wrote:
Hello Pete,
please be aware that the Windows driver we use at the
moment doesn't support isoch (see Known Restrictions for WinUSB at
[1]),
Indeed. Why on earth make WinUSB without isoch support.
It is a low priority
On Fri, May 25, 2012 at 6:24 AM, Yves Arrouye y...@arrouye.net wrote:
How can I do that? Just trying to pass arch flags in CFLAGS/LDFLAGS is
not working:
% make
make all-recursive
Making all in libusb
CC libusb_1_0_la-core.lo
llvm-gcc-4.2: -E, -S, -save-temps and -M options are not
On Fri, May 25, 2012 at 9:37 PM, Fabian Weiss fab...@fabske.de wrote:
What exactly do you mean by communication protocol? I know what is in
the 42 bytes I am expecting to receive from the USB device.
Do you think I first have to send something to the device?
You have to know that. You may well
On Fri, May 25, 2012 at 2:41 PM, Kyle McKay mack...@gmail.com wrote:
cd /tmp
git clone git://libusbx.git.sourceforge.net/gitroot/libusbx/libusbx
cd libusbx
git log -1 --oneline
# a544e59 Misc: Ensure all sources are UTF-8
./autogen.sh
CFLAGS='-O2 -arch x86_64 -arch i386 -arch ppc' \
On Thu, May 24, 2012 at 11:39 PM, Pete Batard p...@akeo.ie wrote:
This one should work a bit better.
Tested under Mac OS X Lion.
I am not so sure why there is the last warning about pipe stall.
The first two warning messages are because of the Apple
USB Bluetooth controller.
+++
On Fri, May 25, 2012 at 2:01 AM, Pete Batard p...@akeo.ie wrote:
This one does a few things:
1. It sets the origin of the timestamps to the first libusb_init() call
issued by the application. The idea is to avoid getting an arbitrary origin
once we have toggleable logging, as it is currently
On Sat, May 26, 2012 at 6:26 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Fri, May 25, 2012 at 2:01 AM, Pete Batard p...@akeo.ie wrote:
This one does a few things:
1. It sets the origin of the timestamps to the first libusb_init() call
issued by the application. The idea is to avoid getting
On Sat, May 26, 2012 at 6:35 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Sat, May 26, 2012 at 6:26 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Fri, May 25, 2012 at 2:01 AM, Pete Batard p...@akeo.ie wrote:
This one does a few things:
1. It sets the origin of the timestamps to the first
On Mon, May 28, 2012 at 6:49 PM, Pete Batard p...@akeo.ie wrote:
If you look at the git log [1], you'll see that the following have now
been pushed:
- Topology calls
- Fix for Trac #1 (adjust OS X log severity)
- minor log level improvements (log levels in libusb.h and timestamp
origin on
News:
http://www.phoronix.com/scan.php?page=news_itempx=MTEwNTY
And then there are various websites following that news.
The news actually links to Hans' blog post here.
http://hansdegoede.livejournal.com/12524.html
Fedora libusbx switch review request here.
I sent the following post to NetBSD current-user list and
the response is quite good.
http://mail-index.netbsd.org/current-users/2012/05/30/msg020270.html
Now libusb-1.0, libusbx and libusb-compat are in pkgsrc now.
And we will probably see binaries for NetBSD soon as well.
On Sun, Jun 3, 2012 at 7:12 PM, Chuck Cook cmco...@earthlink.net wrote:
libusbx doesn't appear to have made it into the available packages for
Fedora 17. All I find is libusb 1.0.9.rc1 which is very out of date at
this time.
I believe it was too late for Fedora 17 Release and it will probably
Just want to clarify the minimum supported version of automake,
autoconf, libtool and pthread for libusbx.
As per Pete, autoconf needs to be 2.50 minimum. What
about automake? I think probably 1.10 should be the one to go.
I do not see a problem with these two (automake 1.10 and
autoconf 2.50) in
On Tue, Jun 5, 2012 at 9:38 PM, Pete Batard p...@akeo.ie wrote:
What about pthread? I just tried to build libusbx-1.0.11
release under Ubuntu 8.04 (already obsoleted) and it
gives error. I am not saying that libusbx needs to be fixed
to suit for older distros but just wondering what is the
On Tue, Jun 5, 2012 at 9:38 PM, Pete Batard p...@akeo.ie wrote:
On 2012.06.05 03:32, Xiaofan Chen wrote:
libtool is often a problem due to the need to
support Windows.
Eg: for old version of libtool.
./configure: line 3371: LT_INIT: command not found
./configure: line 3372: syntax error
On Wed, Jun 6, 2012 at 6:03 PM, Pete Batard p...@akeo.ie wrote:
I have now pushed the fix for the implicit declaration of function
‘pthread_mutexattr_settype’ error on Linux.
I have tested the change on all the POSIX platforms we support
(including tests on Debian 6.0 and Slackware 13.37),
-- Forwarded message --
From: Lars Kanis l...@greiz-reinsdorf.de
Date: Wed, Jun 6, 2012 at 5:23 PM
Subject: Segfault on win32
To: libusb-de...@lists.sourceforge.net
Hi libusb hackers,
I maintain the libusb-1.0-binding for Ruby (
https://github.com/larskanis/libusb ). The
On Thu, Jun 14, 2012 at 7:50 PM, Pete Batard p...@akeo.ie wrote:
The 2 Clang patches as well as the speed designation patch suggested by
Xiaofan have now been pushed to git.
As changes were applied to core, if you have an opportunity to test
before release, please do so. These warning fixes
On Wed, Jun 13, 2012 at 7:04 PM, Toby Gray toby.g...@realvnc.com wrote:
Sorry, my email client decided to send that email as HTML.
Here is the contents as plain text:
On 13/06/12 11:13, Toby Gray wrote:
Hi,
I've been trying to use libusbx to connect to an Android device via the
Android
On Sun, Jun 17, 2012 at 12:13 PM, Jach Fong jf...@ms4.hinet.net wrote:
Hi! Xiaofan,
Thanks for your prompt reply.
When I first read the libusbx introductory info, I thought the
libusbx has its own driver as the libusb-win32 had. I was wrong:-(
It still need the MS's WinUSB.
If it
On Sun, Jun 17, 2012 at 12:35 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Sun, Jun 17, 2012 at 12:13 PM, Jach Fong jf...@ms4.hinet.net wrote:
When I first read the libusbx introductory info, I thought the
libusbx has its own driver as the libusb-win32 had. I was wrong:-(
It still need
On Sun, Jun 17, 2012 at 7:21 PM, Xiaofan Chen xiaof...@gmail.com wrote:
I found a strange error when building libusbx with newer version of
the dlltool. As per this thread, it is the syntax error of libusb-1.0.def
which caused the problem.
http://comments.gmane.org/gmane.comp.gnu.mingw.w64
On Sun, Jun 17, 2012 at 8:00 PM, Peter Stuge pe...@stuge.se wrote:
Xiaofan Chen wrote:
Bug report to dlltool (actually invalid as pointed by Kai).
http://sourceware.org/bugzilla/show_bug.cgi?id=14258
On the other hand, Ruben disagreed with Kai and he
thinks that the library name
On Sun, Jun 17, 2012 at 7:08 PM, Ellis Whitehead
ellis.whiteh...@gmail.com wrote:
I have a project http://gcead.sourceforge.net/ that records data from
an isochronous acquisition device. The USB communication utilizes
libusbx on linux and libusb-win32 on windows, and both work fine
(thanks!).
To Ellis: please subscribe to the mailing list. Thanks.
On Sun, Jun 17, 2012 at 9:08 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Sun, Jun 17, 2012 at 7:08 PM, Ellis Whitehead
ellis.whiteh...@gmail.com wrote:
I have a project http://gcead.sourceforge.net/ that records data from
On Sat, Jun 16, 2012 at 11:49 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Sat, Jun 16, 2012 at 2:08 AM, Pete Batard p...@akeo.ie wrote:
It is my pleasure to announce the release of libusbx v1.0.12.
Great.
Since you mentioned clang quite a bit, so I tried to build
this one under Mac OS X
On Sat, Jun 16, 2012 at 5:28 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Sat, Jun 16, 2012 at 3:22 AM, Pete Batard p...@akeo.ie wrote:
I don't think I recompiled at level 4 since last time we tried it in
libusb-devel, which was probably more than a year ago.
I have now added this item
On Mon, Jun 18, 2012 at 6:08 PM, Jach Fong jf...@ms4.hinet.net wrote:
I test it today on using the Borland C++ 5.0 (My previous tests
were done on another language).
Wow, that is very old toolchain. Any reason you want to use it?
At first, the BC++ linker complains about the
On Sun, Jun 17, 2012 at 10:33 PM, Ellis Whitehead
ellis.whiteh...@gmail.com wrote:
You can produce detailed debug log if you set the environmental
variable LIBUSB_DEBUG to 4. That debug log may help to identify
the potential problem.
Ok, I've uploaded it here:
Right now libusbx does not have an example to show how to use
the aysnc API. And some users may want to have some simple
examples than dpfp to start with. And 1.0.13 will hopefully
add libusb0.sys and libusbK.sys with isochronous transfer support.
So I think it will be good to add one example in
On Sat, Jun 16, 2012 at 2:08 AM, Pete Batard p...@akeo.ie wrote:
It is my pleasure to announce the release of libusbx v1.0.12.
I found a strange problem under XP 64bit with MinGW.org toolchain.
On the other hand, I am not so sure if this is a real issue since there
is doubt whether XP 64bit
On Mon, Jun 18, 2012 at 10:49 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Sat, Jun 16, 2012 at 2:08 AM, Pete Batard p...@akeo.ie wrote:
It is my pleasure to announce the release of libusbx v1.0.12.
I found a strange problem under XP 64bit with MinGW.org toolchain.
On the other hand, I am
On Tue, Jun 19, 2012 at 8:08 AM, Markus li...@neuronenwerk.de wrote:
On Tue, 19 07:35 , Xiaofan Chen wrote:
http://argh.target23.de/data/fx3.png
That still shows High Speed USB, have you tried it with
the USB 3.0 SuperSpeed port?
The device is attached to a SuperSpeed hostcontroller here
On Fri, Jun 22, 2012 at 11:11 AM, Alan Ott a...@signal11.us wrote:
On 06/16/2012 12:51 PM, Nathan Hjelm wrote:
The only reason to use libusb under hidapi on Linux is the lack of
an HID API. Its not really a good thing.
I disagree. Linux has hidraw, which is its native HID interface from
On Sun, Jun 24, 2012 at 8:27 PM, Ellis Whitehead
ellis.whiteh...@gmail.com wrote:
I had hoped that I could make some progress by investigating this
further myself, but wasn't able to figure much out... It seems to me
in the log file that I posted, the log entry of most interest is this
one:
On Tue, Jun 26, 2012 at 4:52 AM, Nathan Hjelm hje...@me.com wrote:
If the transaction should be working the user could try to change how far in
the future the isoc transaction is scheduled for. He can do this by changing
line 1370 (in 1.0.9) from:
frame += 4;
to
frame += 6;
or something
On Tue, Jun 26, 2012 at 9:08 PM, Pete Batard p...@akeo.ie wrote:
On 2012.06.26 13:48, Timotei Dolean wrote:
Is there any way I (or someone) could be involved/help implememting the
other drivers (like libusb0.sys)? If yes, is there any information
regarding on what/how to contribute?
Well,
On Tue, Jun 26, 2012 at 4:52 AM, Rich von Lehe rhvonl...@gmail.com wrote:
In lieu of set_configuration in this case (there is only one config),
one process would claim_interface 0 and the other process would
claim_interface 1. I have a suspicion that the underlying
implementation in Libusb is
On Thu, Jun 28, 2012 at 9:36 PM, Sean McBride s...@rogue-research.com wrote:
On Wed, 27 Jun 2012 20:39:52 +0200, Ludovic Rousseau said:
We're specifying gnu99 in AM_CFLAGS, so I wouldn't expect it to end up
in LD_FLAGS. This is benign, so I'm not sure it's worth spending time on
fixing that.
On Tue, Jun 26, 2012 at 4:52 AM, Rich von Lehe rhvonl...@gmail.com wrote:
In lieu of set_configuration in this case (there is only one config),
one process would claim_interface 0 and the other process would
claim_interface 1. I have a suspicion that the underlying
implementation in Libusb is
https://libusb.org/ticket/136
Not so sure if this is a real bug or not.
--
Xiaofan
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and
On Tue, Jul 3, 2012 at 5:23 PM, Pete Batard p...@akeo.ie wrote:
On 2012.07.03 08:33, Hans de Goede wrote:
Next time please send patches inline, that makes replying to them for a
review a lot easier.
This is getting old.
The thing is, Segher complained once, so I went inline, then Xiaofan
On Tue, Jul 3, 2012 at 6:04 PM, Pete Batard p...@akeo.ie wrote:
v2, that applies Hans' suggestion.
NB: This patch should be attached as inline
Actually it comes to me as both inline and attachment and both
are with the extra . Kind of strange, either something is wrong
with Gmail or something
On Tue, Jul 3, 2012 at 9:26 PM, Pete Batard p...@akeo.ie wrote:
On 2012.07.03 13:59, Xiaofan Chen wrote:
NB: This patch should be attached as inline
Actually it comes to me as both inline and attachment
Which is exactly what I want.
I see. In that case, no problem.
Pure inline is a PITA
On Wed, Jul 4, 2012 at 12:22 AM, Pete Batard p...@akeo.ie wrote:
On 2012.07.03 14:38, Xiaofan Chen wrote:
I sent the patch both inline and as an attachment using Gmail.
Both are okay from what I see, no extra . But maybe you
will see the for the inline version. Did you see the for
my
On Fri, Jul 13, 2012 at 5:34 PM, Pete Batard p...@akeo.ie wrote:
Hi Dave,
On 2012.07.13 00:08, Dave Camarillo wrote:
Hello, I was wondering what kinds testing has been done on
Mac's with USB 3.0?
None on my end. I don't think any of the regulars here have had access
to a Mac with USB 3.0.
On Sat, Jul 14, 2012 at 1:26 AM, Dave Camarillo
dave.camari...@gmail.com wrote:
On Fri, Jul 13, 2012 at 3:37 AM, Xiaofan Chen xiaof...@gmail.com wrote:
Hopefully the next Mac Mini and iMac will have USB 3.0. And
I may want to buy a new Mac Mini with USB 3.0 in the future.
My current Mac Mini
It seems to me that with the libusbx git version,
libusb-1.0.pc generated does not show the version
information. Strange.
$ cat libusb-1.0.pc
prefix=/usr/local
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: libusbx-1.0
Description: C API for USB device access
On Sat, Jul 28, 2012 at 5:54 PM, Hans de Goede hdego...@redhat.com wrote:
Currently applications for devices which only are accessed from
userspace can use claim / release interface to make sure they
don't get in each others way. The same however does not work
for applications which first need
On Thu, Aug 16, 2012 at 5:07 AM, David Grant davidgr...@gmail.com wrote:
I've looked at using libusb-win32 as a filter driver but it
seems I can only install it as a filter driver for all classes of the
devices that are already plugged in.
That is not true. We provide the capability to install
On Thu, Aug 16, 2012 at 5:32 AM, David Grant davidgr...@gmail.com wrote:
Ok, so that sounds promising. I guess the next question is: is it possible
to use libwdi to install a filter driver for a device, or to replace that
device's driver, take over the device, and then put everything back to
On Wed, Aug 8, 2012 at 7:41 AM, Pete Batard p...@akeo.ie wrote:
All,
If you have some interest with regards to libusb-win32 and libusbK
driver support, you may want to have a look at the new 0K (zero K)
branch from the pbatard/libusbx repo on github [1].
I have now pushed a patch that adds
On Wed, Aug 22, 2012 at 8:04 AM, David Grant davidgr...@gmail.com wrote:
Thanks for the detailed response Pete.
So the big missing feature seems to be how to remove libusbK.sys and replace
it with the original driver without having to embed the original driver.
Currently the original driver
On Tue, Aug 21, 2012 at 5:12 PM, Hans de Goede hdego...@redhat.com wrote:
Signed-off-by: Hans de Goede hdego...@redhat.com
---
libusb/core.c | 4
libusb/os/linux_usbfs.c | 6 ++
2 files changed, 10 insertions(+)
diff --git a/libusb/core.c b/libusb/core.c
index
On Tue, Aug 21, 2012 at 5:10 AM, Hans de Goede hdego...@redhat.com wrote:
+ /*
+* Older versions of usbfs place a 16kb limit on bulk URBs. We work
+* around this by splitting large transfers into 16k blocks, and then
+* submit all urbs at once. it would be simpler
On Mon, Aug 20, 2012 at 8:32 AM, Pete Batard p...@akeo.ie wrote:
Hopefully will help getting more testing before next release.
I'm closing #11 and #12 as a result (isoc support will be dealt elsewhere).
I also pushed the patch provided for #41
(https://github.com/libusbx/libusbx/pull/41).
On Thu, Aug 23, 2012 at 1:55 AM, David Grant davidgr...@gmail.com wrote:
I don't understand why that would be the case. libusb + libusbK seems like
the perfect solution for us especially when we consider the fact that we are
already using libusb in the Linux (x86 + ARM) environments with great
On Fri, Aug 24, 2012 at 4:06 AM, David Grant davidgr...@gmail.com wrote:
On Fri, Aug 17, 2012 at 5:56 PM, Pete Batard p...@akeo.ie wrote:
Now, due to time constraints as well as other considerations
(removing/deleting anything needs to be carefully considered), libwdi
doesn't support
On Thu, Aug 23, 2012 at 7:23 PM, Satz Klauer satzkla...@googlemail.com wrote:
Hi,
I found libusbx via a link at project libusb-winusb-wip and I'm a bit
confused now.
Until now when using old libusb on Windows some WinUSB drivers have
been mandatory (that's what I'm looking for at
On Mon, Aug 27, 2012 at 9:02 AM, John Chen john...@gmail.com wrote:
Hi,I just trying to do a simple bulk read, and always got a TIMEOUT, would
any one please tell me what I did wrong here?
Most likely the device does not understand the command/data your
host program sends to it. For example,
On Mon, Aug 27, 2012 at 7:21 AM, Pete Batard p...@akeo.ie wrote:
On 2012.08.25 10:52, Xiaofan Chen wrote:
It seems to me xusb -k does not work well with some
USB Flash Drive like the Sandisk 8GB drive and a
Kingston 1GB drive I have, even with a real Windows 7
x64 machine.
Yeah, I'm seeing
On Wed, Aug 29, 2012 at 9:30 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Wed, Aug 29, 2012 at 8:01 AM, Pete Batard p...@akeo.ie wrote:
Now, with regards to where in libusbx or libusbK lies the problem, in
xusb, we do call libusb_bulk_transfer() and tell it we expect 36 bytes,
which is what K
Here are two links from libusb mailing list, saying to include the
extra libraries needed for static linking in Libs.private in the pc file.
http://libusb.6.n5.nabble.com/libusb-1-0-pc-files-when-static-linking-td43.html
On Tue, Sep 4, 2012 at 4:46 PM, Ludovic Rousseau
ludovic.rouss...@gmail.com wrote:
2012/9/4 Xiaofan Chen xiaof...@gmail.com:
Here are two links from libusb mailing list, saying to include the
extra libraries needed for static linking in Libs.private in the pc file.
http://libusb.6.n5
On Thu, Sep 6, 2012 at 6:26 AM, Pete Batard p...@akeo.ie wrote:
OK, IMO, the best way to address that last issue we have with libusb0 as
composite device is by modifying the libusb0 inf file to create a Device
Interface GUID during installation.
In this case, this is really a one liner change
On Thu, Sep 6, 2012 at 8:03 AM, Pete Batard p...@akeo.ie wrote:
Since we need to gear up for the 1.0.13 release, I have just pushed back
a few of the tasks that we had planned but that I don't really see
happening over the next few days, into 1.0.14. These include:
- Adding the WinCE backend
On Tue, Sep 4, 2012 at 6:45 AM, Pete Batard p...@akeo.ie wrote:
Just an update. I now have a partial patch for composite support, that
appears to works fine with WinUSB and libusbK, but still doesn't
properly set the interfaces for libusb0.
Just checked the latest git and it indeed solved the
On Thu, Sep 6, 2012 at 9:56 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Thu, Sep 6, 2012 at 6:26 AM, Pete Batard p...@akeo.ie wrote:
OK, IMO, the best way to address that last issue we have with libusb0 as
composite device is by modifying the libusb0 inf file to create a Device
Interface
1 - 100 of 398 matches
Mail list logo
