On Mon, May 28, 2012 at 6:56 PM, Pete Batard wrote:
> On 2012.05.28 11:53, Xiaofan Chen wrote:
>>> Basically, xusb will try to access string descriptor 0xEE to find out if
>>> the device is WCID and display the WCID data if that is the case (which
>>> can be done on any platform, not just Windows)
On 2012.05.28 11:53, Xiaofan Chen wrote:
>> Basically, xusb will try to access string descriptor 0xEE to find out if
>> the device is WCID and display the WCID data if that is the case (which
>> can be done on any platform, not just Windows). It looks like trying to
>> access 0xEE on Mac produces a
On Mon, May 28, 2012 at 6:45 PM, Pete Batard wrote:
> On 2012.05.26 11:05, Xiaofan Chen wrote:
>> I am not so sure why there is the last warning about pipe stall.
>>
>> Claiming interface 0...
>>
>> Reading string descriptors:
>> String (0x01): "SEGGER"
>> String (0x02): "J-Link"
>> St
Pete Batard wrote:
> It looks like trying to access 0xEE on Mac produces a pipe stall.
Doesn't that make sense actually, for devices which don't have that
string descriptor?
//Peter
--
Live Security Virtual Conference
E
On 2012.05.26 11:05, Xiaofan Chen wrote:
> I am not so sure why there is the last warning about pipe stall.
>
> Claiming interface 0...
>
> Reading string descriptors:
> String (0x01): "SEGGER"
> String (0x02): "J-Link"
> String (0x03): ""
> libusbx: warning [darwin_transfer_sta
On Thu, May 24, 2012 at 11:39 PM, Pete Batard 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.
+++
mymacmini:examples
This one should work a bit better.
Regards,
/Pete
>From 67abd67778893631da0e822b57feef68cf9208e4 Mon Sep 17 00:00:00 2001
From: Pete Batard
Date: Thu, 24 May 2012 11:42:47 +0100
Subject: [PATCH 2/2] Darwin: Align severity of OS-X logging messages
* Some informational messages were actually de
