On Sat, Jul 14, 2012 at 1:26 AM, Dave Camarillo
wrote:
> On Fri, Jul 13, 2012 at 3:37 AM, Xiaofan Chen 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 2011 works great once I upgraded the
[pbatard][1] closed [issue 31][2] on [libusbx/libusbx][3] July 13, 2012
> libusbx-1.0.12 breaks libusb-compat compilation
[1]: https://github.com/pbatard
[2]: https://github.com/libusbx/libusbx/issues/31 (libusbx-1.0.12 breaks
libusb-compat compilation)
[3]: https://github.com/libusbx/
[pbatard][1] commented on [issue 31][2] on [libusbx/libusbx][3] July 13, 2012
> With the LIBUSB_ prefix added, libusb-compat should compile without errors
against libusbx. Closing this issue.
[1]: https://github.com/pbatard
[2]: https://github.com/libusbx/libusbx/issues/31#issuecomment-697
[pbatard][1] commented on [issue 28][2] on [libusbx/libusbx][3] July 13, 2012
> That's good news. I was hoping that this would be the case, so I'll be
closing the issue. Many thanks for following up and reporting back.
[1]: https://github.com/pbatard
[2]: https://github.com/libusbx/libusbx
[pbatard][1] closed [issue 28][2] on [libusbx/libusbx][3] July 13, 2012
> Allow http access to the git repo
[1]: https://github.com/pbatard
[2]: https://github.com/libusbx/libusbx/issues/28 (Allow http access to the
git repo)
[3]: https://github.com/libusbx/libusbx
URL: https://github
On 2012.07.13 16:46, Toby Gray wrote:
> Would keeping a list of the registered device handles
> (dev_info_data.DevInst) with each device and compare against that list
> be better? It then would at least avoid multiple string comparisons.
Currently, I'm thinking that what we probably want is avoid
[larskanis][1] commented on [issue 28][2] on [libusbx/libusbx][3] July 13,
2012
> Now that libusbx has officially moved to github, http(s) access to the repo
is possible, too. The issue is solved therefore.
[1]: https://github.com/larskanis
[2]: https://github.com/libusbx/libusbx/issues/28
On Fri, Jul 13, 2012 at 3:37 AM, Xiaofan Chen wrote:
> On Fri, Jul 13, 2012 at 5:34 PM, Pete Batard 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
Hi Pete,
On Fri, Jul 13, 2012 at 2:34 AM, Pete Batard 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 U
This commit has now been pushed in the new github repo.
See https://github.com/libusbx/libusbx/commits/master
Note that from this commit onward, github is the only libusbx repository
that will see new commits. The now obsolete SourceForge repositories
will not be updated.
Regards,
/Pete
-
All,
If you have been pulling from the current SourceForge git repo, you will
notice that we have just pushed a commit inviting you to update your git
URL, and use git://github.com/libusbx/libusbx.git.
Alternatively, you can also have a look at
https://github.com/libusbx/libusbx for other opti
On 12/07/12 18:00, Pete Batard wrote:
>> The attached patch fixes this by not adding the same interface path
>> twice. It also adds a check for the interface table getting full.
> Ideally I don't think we want to call set_hid_interface() more than we
> need to, which is what happens here. So while
On 13/07/12 14:06, Pete Batard wrote:
>> I've put an alternative fix into the branch which I plan to keep rebased
>> on libusbx/master:
>> https://github.com/tobygray/libusbx/commit/4b0f2413ae85d197db8721e2fda5a85355d95e1b
>>
>> The only thing I'm not sure of in this fix is that wince_usb.c doesn't
On 12/07/12 19:31, Peter Stuge wrote:
> Hi Toby,
>
> As Pete likes to point out I have no authority in the libusbx
> project, so as far as libusbx is concerned I think the best
> might be if you could pretend that I had never posted this
> feedback on the libusbx list.
Thank you for spending time
On 07/13/2012 09:06 AM, Pete Batard wrote:
> On 2012.07.13 12:56, Toby Gray wrote:
>> Firstly I apologise for sending my message body as HTML, I've clearly
>> not figured out how to force Thunderbird to always send as plain text.
>
Go into the thunderturkey address book, edit the libusb-devel ent
On 2012.07.13 12:56, Toby Gray wrote:
> Firstly I apologise for sending my message body as HTML, I've clearly
> not figured out how to force Thunderbird to always send as plain text.
No worries. Text is more friendly for archiving and dumb processing, so
that's what we prefer, but we're not gonna
Firstly I apologise for sending my message body as HTML, I've clearly
not figured out how to force Thunderbird to always send as plain text.
On 12/07/12 20:59, Pete Batard wrote:
>>> 0004 - Replaces getenv() with NULL on WinCE due to it not being supported.
>> Try to change this in a good way whe
On 2012.07.13 11:48, Xiaofan Chen wrote:
> But then the
> problem is that I am not 100% sure if you can get WHQL for a
> class of USB device (no specific VID/PID). It seems to be a
> reserved privilege of Microsoft.
Well, the Windows *Phone* division of Microsoft certainly took that
privilege to
[pbatard][1] commented on [issue 35][2] on [libusbx/libusbx][3] July 13, 2012
> Thanks for this. I'm tentatively going to target this integration against
the 1.0.13 milestone (still needs review).
>
> I also plan to apply [tobygray/libusbx@93e382d][4] to libusbx master soon,
as this isn't direct
[tobygray][1] opened [issue 35][2] on [libusbx/libusbx][3] July 13, 2012
> Integrate experimental WinCE backend
[1]: https://github.com/tobygray
[2]: https://github.com/libusbx/libusbx/issues/35 (Integrate experimental
WinCE backend)
[3]: https://github.com/libusbx/libusbx
URL: https:
On Fri, Jul 13, 2012 at 12:05 AM, Pete Batard wrote:
> On 2012.07.12 14:02, Xiaofan Chen wrote:
>> I think this is a good for Microsoft's part. WinUSB will play an important
>> role in the future and more and more USB device will use WinUSB
>> as the driver down the road and not using the generic
On Fri, Jul 13, 2012 at 5:34 PM, Pete Batard 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. Mac
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. Macs with 3.0 ports are fairly new and still
relatively uncommon, ri
23 matches
Mail list logo
