On Sat, 26 May 2012 11:56:57 +0800, Xiaofan Chen said:
>Great. Under Mac OS X Lion, it seems to me I need to remove
>"-arch ppc". Other than that, it works nicely.
The default compiler on 10.7 doesn't support PPC, which probably explains that.
--
v2. There were a couple more mentions of stdout in the doc that needed
amending.
Regards,
/Pete
>From e88ea2299a695337b0e6dda0b81cfde0018437d1 Mon Sep 17 00:00:00 2001
From: Pete Batard
Date: Mon, 28 May 2012 12:33:18 +0100
Subject: [PATCH] Core: Send all logging output to stderr
* This effec
On 2012.05.28 12:23, Xiaofan Chen wrote:
> Thanks for the updates. Just tried it and there are some warnings
> when build with --disable-log.
Thanks for the test. I guess I'll try to address those with the
harmonizing of the log level for stalled pipe.
Regards,
/Pete
--
A follow up to Ludovic's previously reported issue.
Note that this is only a proposal at this stage.
Regards,
/Pete
>From 44c4969f55191e1a3f833ba6b535ba5a67e47d30 Mon Sep 17 00:00:00 2001
From: Pete Batard
Date: Mon, 28 May 2012 12:33:18 +0100
Subject: [PATCH] Core: Send all logging output to s
Hi,
On 05/25/2012 10:54 PM, Alan Stern wrote:
> On Fri, 25 May 2012, Hans de Goede wrote:
>
>> To verify my theory, I've tried raising the packet splitting limit in
>> libusb to 32k and that (unsurprisingly) fixes things, but that is just
>> a bandaid and not a proper fix for the issue at hand IMH
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 Mon, May 28, 2012 at 6:49 PM, Pete Batard wrote:
> If you look at the git log [1], you'll see that the following have now
> been pushed:
>
> - Topology calls
> - Fix for Trac #1 (adjust OS X log severity)
> - minor log level improvements (log levels in libusb.h and timestamp
> origin on init)
>
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:
> On 2012.05.27 09:27, Peter Stuge wrote:
> > It would probably be simpler to do the same thing by moving the
> > setting of first to before the loglevel check within the logging
> > function.
>
> Except there's no guarantee that the logging function will be called
> during ini
On Mon, May 28, 2012 at 6:46 PM, Pete Batard wrote:
> On 2012.05.26 12:16, Xiaofan Chen wrote:
> Again, don't think there's much point looking at -d of xusb before we
> have toggleable logging.
>
Thanks. That was what I thought as well when I wrote "Maybe
what I really need is the next Toggle-abl
If you look at the git log [1], you'll see that the following have now
been pushed:
- Topology calls
- Fix for Trac #1 (adjust OS X log severity)
- minor log level improvements (log levels in libusb.h and timestamp
origin on init)
- reinstate HID support
Note that there was a minor alteration t
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.27 09:27, Peter Stuge wrote:
> It would probably be simpler to do the same thing by moving the
> setting of first to before the loglevel check within the logging
> function.
Except there's no guarantee that the logging function will be called
during init at all to set the origin, espec
On 2012.05.26 12:16, Xiaofan Chen wrote:
>> Hmm, it does seem to work. "xusb -d" is probably different
>> and strangely it does not seem to honor the LIBUSB_DEBUG environment
>> variable.
Note that the -d option of xusb came from toggleable logging, since it
relies on set_debug which of course wo
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
16 matches
Mail list logo
