On Tue, Mar 12, 2013 at 2:10 PM, Marcus Meissner wrote:
> On Mon, Mar 11, 2013 at 03:30:19PM -0700, Sarah Sharp wrote:
>> On Sat, Mar 09, 2013 at 09:16:53PM +0100, Marcus Meissner wrote:
>> > On Thu, Feb 28, 2013 at 09:32:05AM -0800, Sarah Sharp wrote:
>> > > On Thu, Feb 28, 2013 at 04:59:36PM +01
On Wed, Mar 13, 2013 at 7:20 AM, Pete Batard wrote:
>> BTW, I believe quite some of the USB device only use the
>> EEPROM for the VID/PID (for Windows driver loading) and then
>> it seems to me the firmware hex is still download on the fly to the
>> RAM and run from there.
>
> Yeah, that's what I
On Wed, Mar 13, 2013 at 12:52 AM, Richard Hughes wrote:
>> As per his post to libusb-win32 mailing list, he will
>> probably drop libusb-1.0A support and use his own
>> USB implementation in the future
>
> Shouldn't this trigger some kind of alarm in the libusbx project? I
> mean, if users like Gr
On 2013.03.12 05:08, Xiaofan Chen wrote:
> I think by "Flashing a firmware" you mean to be able to program the
> EEPROM, right?
Yeah. Force of habit from dealing with other devices.
> In that case, here is a patched version of fxload which can do
> that. You may want to take a look at it and inte
Thanks!
Since we need to get moving towards release, I pushed them both.
Regards,
/Pete
PS: I'm switching to using "OS X:" rather than "Darwin:" as the prefix
for the platform, as I think it'll provide higher visibility for Apple
folks. Yeah, I know that technically Darwin is more correct tha
Hi Richard,
I guess I'll bite, and fill you in on a few details, to try to offer a
different perspective from what you seem to _perceive_.
The first thing you need to realize is that we're not Apple or Microsoft
here, or can rely on people people living off of a retirement fund ,with
the luxur
On 12 March 2013 14:05, Xiaofan Chen wrote:
>> * libusb_resetep
> Not implemented yet.
> Ref: https://github.com/libusbx/libusbx/issues/18
Seems no-one is interested. :(
>> * libusb_handle_events_check
> This is probably an extension by Graeme.
Seems to be discussed in http://www.libusb.org/tic
On Tue, Mar 12, 2013 at 11:33 PM, Xiaofan Chen wrote:
>
> The following is for #99, modified from the libusb.org ticket #165.
> I think the original patch there is flawed since it does not consider
> Super Speed where Mac OS X 10.8.x supports.
>
> From 4f22847d7d25ccb5caedfa8b72bc18167c9fabee Mon
On Tue, Mar 12, 2013 at 11:18 PM, Xiaofan Chen wrote:
> On Fri, Mar 8, 2013 at 1:55 PM, Xiaofan Chen wrote:
>> On Thu, Mar 7, 2013 at 11:34 AM, Xiaofan Chen wrote:
>>> I have removed some of the Mac OS X thingy from 1.0.15. They
>>> are good to have but not necessary.
>>
>> Now only issue #83, i
On Fri, Mar 8, 2013 at 1:55 PM, Xiaofan Chen wrote:
> On Thu, Mar 7, 2013 at 11:34 AM, Xiaofan Chen wrote:
>> I have removed some of the Mac OS X thingy from 1.0.15. They
>> are good to have but not necessary.
>
> Now only issue #83, issue #98 and issue #102 are listed under
> 1.0.15 milestone.
>
On Tue, Mar 12, 2013 at 10:10 PM, Xiaofan Chen wrote:
> As per the changelog, libusb support has been dropped since
> 1.5.0, so even if the libusb-1.0A codes are still there, I am not so sure
> whether they are supported by the upstream author (Graeme) or not.
Ref: http://www.argyllcms.com/doc/Ch
On Tue, Mar 12, 2013 at 10:05 PM, Xiaofan Chen wrote:
> As per his post to libusb-win32 mailing list, he will
> probably drop libusb-1.0A support and use his own
> USB implementation in the future. So I am not so sure
> if your efforts will pay off that much. You could just
> use his libusb-1.0A i
On Tue, Mar 12, 2013 at 6:40 PM, Richard Hughes wrote:
> I'm trying to build Argyllcms 1.5.1 for Fedora using the libusbx code
> rather than the internal USB implementation. Using the system
> libraries rather than bundled libraries is best practice for most
> distros, so I'm trying this way first
Hi all,
I'm trying to build Argyllcms 1.5.1 for Fedora using the libusbx code
rather than the internal USB implementation. Using the system
libraries rather than bundled libraries is best practice for most
distros, so I'm trying this way first.
ArgyllCMS seems to require the following functions,
14 matches
Mail list logo
