On Fri, Apr 20, 2012 at 8:21 PM, Jose Pablo josepablo.cas...@gmail.comwrote:
What If I use a software which uses libusb-1.0 and then I decide to
install another software which use libusbx-1.0? Do I have to uninstall the
first one to uses the second one? Just because you people can´t decide not
On Tue, May 1, 2012 at 2:17 PM, Pete Batard p...@akeo.ie wrote:
On 2012.04.29 06:42, Arnon Gilboa wrote:
I see that you used wdi_register_logger() in an Hack for wdi logging
section (currenlty disabled).
Can you elaborate on the limitation you found there and if you would
like an
On Wed, May 2, 2012 at 6:54 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Thu, May 3, 2012 at 4:31 AM, Hans Petter Selasky hsela...@c2i.net
wrote:
On Wednesday 02 May 2012 21:15:27 Tim Roberts wrote:
Hans Petter Selasky wrote:
Why Microsoft can't use the BSD or Linux USB stack then,
On Wed, May 23, 2012 at 4:43 AM, Pete Batard p...@akeo.ie wrote:
On 2012.05.23 03:17, Yves Arrouye wrote:
I double-checked the actual OS X API (the 32 bits comes from one of
their samples). It seems like the underlying object is actually an
OSNumber, which is a wrapper for a kernel number
On Fri, Jun 15, 2012 at 11:08 AM, Pete Batard p...@akeo.ie wrote:
All,
It is my pleasure to announce the release of libusbx v1.0.12.
In terms of bugfixes and new features, this new version brings the
following improvements:
* Fix a potential major regression with pthread on Linux
* Fix
Since I have a copy, I compiled 1.0.12 with the Intel Compiler. I turned
off the zero length array and unreferenced parameter warnings. This is
what is left:
Building with Intel(R) C++ Compiler 12.1
ClCompile:
* ClCompile (Win32 - Intel C++)
All outputs are up-to-date.
core.c
On Thu, Jun 21, 2012 at 1:08 PM, Pete Batard p...@akeo.ie wrote:
I'm gonna bump the priority of churning through the warnings, else I'm
pretty sure they're going to fall through.
Proposed patch attached. Please let me know if still get reports for the
ones mentioned below.
All but the
I've seen the list get screwed up by trying to reissue a transfer before
getting the callback. The list got a circular segment in that case.
Perhaps something like cancelling a transfer followed by freeing it before
getting the callback causes this?
I made a couple of changes to trap this - I'll
On Thu, Aug 2, 2012 at 9:30 AM, Orin Eman orin.e...@gmail.com wrote:
I've seen the list get screwed up by trying to reissue a transfer before
getting the callback. The list got a circular segment in that case.
Perhaps something like cancelling a transfer followed by freeing it before
getting
On Thu, Aug 9, 2012 at 4:57 PM, Jon Sturm jonimo...@gmail.com wrote:
On Thu, Aug 9, 2012 at 3:01 AM, Markus li...@neuronenwerk.de wrote:
Hi Pete,
my answers became a bit longer than intended. Here's my 5 cent,
but generally, I'd leave the decision to you:
Now, this being said, I
On Sun, Sep 2, 2012 at 7:15 AM, Hans de Goede hdego...@redhat.com wrote:
Hi,
On 09/02/2012 03:47 AM, Pete Batard wrote:
On 2012.08.31 20:40, Hans de Goede wrote:
This assumes that the winusb flag causes the ep to halt when the short
read is encountered
Couldn't see much in NetMon,
On Sun, Sep 2, 2012 at 2:15 PM, Alan Stern st...@rowland.harvard.eduwrote:
On Sun, 2 Sep 2012, Orin Eman wrote:
Then as said that is a pretty useless feature, since apps can already
find out as much by comparing the amount actually read versus the
amount
they requested
On Wed, Sep 12, 2012 at 4:40 PM, Pete Batard p...@akeo.ie wrote:
On 2012.09.12 10:51, Hans de Goede wrote:
should we add a new API even if we
expect at least one for the platforms we support never to have any use
for it?
Yes, I want libusbx to enable app writers to do whatever they
On Mon, Sep 24, 2012 at 12:35 PM, Pete Batard p...@akeo.ie wrote:
On 2012.09.24 20:31, Greg KH wrote:
No one delivered any such fix, all I got was a bunch of bug reports
this morning from the distros saying that usbutils was suddenly broken.
That shows that libusbx is really the problem
On Mon, Oct 15, 2012 at 7:58 PM, Pete Batard p...@akeo.ie wrote:
On 15 October 2012 12:15, Sean McBride s...@rogue-research.com wrote:
3) Look at how other software that uses -Wcast-align handles the same
issue.
I'm not exactly sure what you're asking...
I was suggesting that, before we
On Mon, Dec 10, 2012 at 5:23 PM, Peter Stuge pe...@stuge.se wrote:
Peter Stuge wrote:
Are there considerations (timing? something else?)
related to asking Windows for memory as needed
Pete Batard wrote:
Adding and testing array reallocation code is a PITA
and development time is always
On Tue, Feb 12, 2013 at 2:38 PM, Nathan Hjelm hje...@me.com wrote:
On Feb 12, 2013, at 3:41 AM, Kustaa Nyholm kustaa.nyh...@planmeca.com
wrote:
On 12.2.2013 12.29, Hans de Goede hdego...@redhat.com wrote:
I know, but I'm operating under the assumption that Nathan will
eventually
do a
On Sat, Mar 30, 2013 at 6:00 AM, Kustaa Nyholm
kustaa.nyh...@planmeca.comwrote:
Hi,
sorry for the OT but I felt the expertise on this
list might have answer on tap.
I've got a .inf file for my USB CDC ACM device
that works fine. However installing it requires
about million steps for the
On Thu, May 30, 2013 at 2:30 AM, Hans de Goede hdego...@redhat.com wrote:
Hi,
On 05/30/2013 09:44 AM, Xiaofan Chen wrote:
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
I'm pretty sure I use some form of handle events with timeout in the thread
that I use to handle events. Each time the thread wakes up, it checks a
run flag and if the flag is reset, the thread exits. When it wants the
event handler thread to quit, the main code resets the run flag and waits
for
If an EFAULT return from the kernel results in an infinite loop in
libusb(x):
It's not a matter of _recovering_ from the EFAULT. It's a matter of
whether libusb(x) should propagate it to the caller or not.
There is simply _no_ excuse not to propagate it.
Sarcasm on
Should we tell the kernel
I've not met an MSVC compiler that hasn't implemented {0} correctly.
Perhaps it's the comma Xcode doesn't like: {0,} and {0} would be OK.
(Assuming the comma in the original post wasn't a typo.)
I haven't compiled libusb(x) on the Mac since I got forced into installing
Xcode 5... I'll give it a
22 matches
Mail list logo
