Hi,
It with pleasure that I would like to announce the release of libusbx
1.0.13. This version brings the following notable changes:
* [MAJOR] Fix a typo in the API with struct libusb_config_descriptor
where MaxPower was used instead of bMaxPower, as per the specs.
If your application was a
On 2012.09.24 18:24, Greg KH wrote:
I don't think so. Remember, usbutils is the _one_ libusb package that
everyone has on their system. The fact that the libusbx release wasn't
tested with that package makes me wonder how it was tested at all.
Greg,
We made the conscious decision to potentia
On 2012.09.24 19:50, Greg KH wrote:
Please fix this in libusbx, or bump the .so name so that tools can
properly know that the API has changed, and that they want to build
against the old one.
Well, if you leave us no other alternative, then I guess my vote will be
for option 2, especially as w
re.
Could you please have a look at the release note that was posted on this
list? We did our best to ensure the possibility of breakage featured
prominently.
The full content of the post is replicated below.
Regards,
/Pete
On 2012.09.20 22:42, Pete Batard wrote:> Hi,
>
> It with pleas
On 2012.09.24 20:26, Greg KH wrote:
I would ask how this library update was tested if someone didn't, at the
very least, test the most common application that uses the library?
Ad hoc, and mostly, as far as I'm concerned, using our sample xusb and
fxload test application and a selected list of
a.k.a. "1.0.13, we hardly knew ye".
* Reverts the previous API change with regards to bMaxPower.
* Note that LIBUSBX_API_VERSION is *decreased* to 0x01FF and the
previous guidelines with regards to concurrent use of
MaxPower/bMaxPower still apply.
Regards,
/Pete
--
To unsubscribe from t
Hi,
The 2nd release candidate for libusbx v1.0.15 is now available at
http://sourceforge.net/projects/libusbx/files/releases/1.0.15/source/
This version brings the following improvements:
* Improve tranfer cancellation and avoid short read failures on broken
descriptors
* Filter out 8-bit ch
On 2013.04.04 09:27, nico wrote:
Making all in libusb
CC libusb_1_0_la-core.lo
core.c:1755:30: warning: use of logical '&&' with constant operand
Thanks for the report, and the test.
This is now fixed in RC3, along with a couple minor issues.
The new RC is available from:
http://sourcef
On 2013.04.09 11:39, nico wrote:
can someone provide a MinGW 32bits built of the last working RC,
Sure. Please have a look at the -win download from:
https://sourceforge.net/projects/libusbx/files/releases/1.0.15/binaries/
The Windows binary contains the 32 and 64 bit versions of both the
sta
Hi,
Libusbx v1.0.15 has now been released. A source tarball is available at:
http://sourceforge.net/projects/libusbx/files/releases/1.0.15/source/
This version brings the following fixes and improvements:
* Improve transfer cancellation and avoid short read failures on broken
descriptors
* Fil
Hi,
It is my great pleasure to announce the release of libusb 1.0.18 (as
well as the simultaneous final release of libusbx 1.0.18), which marks
the long awaited merging back of libusbx with libusb!
With this release, we are finally consolidating the two projects back
into one, and bringing t
On 2014.01.26 07:47, Peter Stuge wrote:
I've removed the libusbx-devel list since Pete Batard banned[1] me
after I wrote that I considered the libusbx code to have a bug[2].
Here we go again. Well, we've been through that quite a few times already.
In the thread you pointed, I exp
Hi Jens,
On 2014.01.27 12:25, Jens Bauer wrote:
On Sun, 26 Jan 2014 17:07:42 +, Pete Batard wrote:
I, and many others, happen to think users of libusb deserve more than
one release in 4 years, even more so as continuous major development has
been going on.
I disagree.
If libusb works
On 2014.01.27 20:44, Jens Bauer wrote:
Pete, you are young
Not a good start.
What if I told you I started programming in the mid 80s? Do I still qualify?
But you have a problem. You feel attacked whenever anyone says something that
you do not agree with.
Yes, I tend to be annoyed when peo
14 matches
Mail list logo
