> > I think it turned out very good once
> > it was done, but anyway, everyone is busy working on new and even
> > better versions now. :)
>
> It is probably good enough for Mac OS X and Linux. But on Windows,
> libusb-1.0.9 is basically not usable due to missing important fixes.
> And even under L
On Wed, Sep 26, 2012 at 10:17 AM, Peter Stuge wrote:
> Alas I had tunnel vision on the master branch, noone helped me out of
> that, and 1.0.9 took too long.
Glad that you recognized that.
> I think it turned out very good once
> it was done, but anyway, everyone is busy working on new and even
Lionel Debroux wrote:
> The maintainer of libusb has proved, for two years, to be a roadblock on
> the path of advancing the state of libusb and on making life easier for
> users.
I think it would be fair of you to look closely at the repository
history before we discuss if and how I advanced the
On Wed, Sep 26, 2012 at 4:00 AM, Frank Hibbeln wrote:
> Sorry - I cant seem to find a "Reply" link for a message ( 29869217 ) posted
> by Chuck Cook 2012-09-22 to the list so I hope this will find its way.
>
> The OS is Windows XP. The app is being built with VStudio 2010.
Did you install the sup
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
--
Note that I had to revert a commit in github, as the initial 1.0.14
release broke the Windows backend, that had been updated to bMaxPower.
If you have been unlucky to pull from git within the last couple of
hours, expect git to be unhappy.
Also, since now of usbutils patches proposals I saw app
Sorry - I cant seem to find a "Reply" link for a message ( 29869217 )
posted by Chuck Cook 2012-09-22 to the list so I hope this will find its
way.
The OS is Windows XP. The app is being built with VStudio 2010.
Thanks
Frank
On Tue, Sep 25, 2012 at 09:57:45AM +0200, Hans de Goede wrote:
> want to know about this>
Thanks for this, I do.
> On 09/25/2012 01:41 AM, Pete Batard wrote:
> >OK, since I'd like to use the 1.1 version change as an opportunity to
> >slide in a couple more API changes (set transfer codes to nega
On Wed, Sep 12, 2012 at 7:05 AM, Xiaofan Chen wrote:
> On Fri, Jul 13, 2012 at 7:08 AM, Dave Camarillo
> wrote:
>> Hello, I was wondering what kinds testing has been done on Mac's with USB
>> 3.0?
>>
>> I happened to get a hold of a new mac with USB 3.0 and tried out our
>> software on it, which
2012/9/25 Hans de Goede :
> On 09/25/2012 01:41 AM, Pete Batard wrote:
>> OK, since I'd like to use the 1.1 version change as an opportunity to slide
>> in a couple more API changes (set transfer codes to negative, as well as
>> #21, and possibly libusb_strerror), but I doubt people will want to
Hello,
2012/9/24 Greg KH :
> On Mon, Sep 24, 2012 at 08:35:07PM +0100, Pete Batard 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
Hi,
On 09/25/2012 09:57 AM, Hans de Goede wrote:
And 2 minutes after pressing send I realize I missed one, I guess we better
put this list on the wiki somewhere or some such ...
> So for the list of desired API changes, for 1.1 you've planned AFAIK:
>
> 1) The bMaxPower change
> 2) Make transfer
Hi,
On 09/25/2012 01:41 AM, Pete Batard wrote:
> OK, since I'd like to use the 1.1 version change as an opportunity to slide
> in a couple more API changes (set transfer codes to negative, as well as #21,
> and possibly libusb_strerror), but I doubt people will want to wait a week or
> so, we
13 matches
Mail list logo
