Re: [Libusbx-devel] libusbx milestone dicussion

2013-03-13 Thread Xiaofan Chen
On Fri, Mar 8, 2013 at 2:16 PM, Xiaofan Chen wrote: > For 2.0 release, I think we label it as "API change only" release > unless critical bug fixes are required. Let's keep it that way. > I will not add any other issues to the 2.0 milestone unless there > are other API changes required. > https://

Re: [Libusbx-devel] Samples: Add FX3 firmware upload support for fxload

2013-03-13 Thread Xiaofan Chen
On Thu, Mar 14, 2013 at 9:24 AM, Pete Batard wrote: > On 2013.03.13 05:22, Xiaofan Chen wrote: > http://dx.com/p/d1201-ez-usb-fx2lp-cy7c68013a-usb-development-board-blue-179473 > for less than €10/$13 with free (but very lengthy) shipping. > There's also e-bay where CY7C68013A clones should be eas

Re: [Libusbx-devel] Samples: Add FX3 firmware upload support for fxload

2013-03-13 Thread Pete Batard
On 2013.03.13 05:22, Xiaofan Chen wrote: > It is a simple board and there are many similar boards like this > in the web. Some of them are quite cheap (US$10 - US$20, but the > shipment can be a problem). > http://detail.tmall.com/item.htm?spm=a230r.1.10.1.al4bvD&id=16344323104 > http://item.taobao

Re: [Libusbx-devel] Functions needed by argyllcms

2013-03-13 Thread Pete Batard
On 2013.03.13 07:07, Richard Hughes wrote: >>From my (perhaps naive) point of view, it seems much more priority is > being given to edge features like WinCE support, rather than core > issues with the library. Glad you make that point, as it'll give me an opportunity to explain a few things. Fir

Re: [Libusbx-devel] USB3 Error

2013-03-13 Thread Sarah Sharp
On Wed, Mar 13, 2013 at 01:37:35PM +0800, Xiaofan Chen wrote: > 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 -

Re: [Libusbx-devel] Feature request: plug-in notification.

2013-03-13 Thread Tim Roberts
Bent Bisballe Nyeng wrote: > In the time I have been using libusb there has always been a single > feature that I was missing: The ability to get a notification when a new > device is connected (or disconnected for that matter), and thereby > remove the need for continuous rescans of the usb bus. >

Re: [Libusbx-devel] Feature request: plug-in notification.

2013-03-13 Thread Bent Bisballe Nyeng
Thank you very much for your reply. This seems to be exactly what I was looking for. I can't believe I missed it on the roadmap. The disrupted file transfer is a windows only thing and to be honost I have not tried it with libusbx, only libusb-1.0.8 so things might behave differently today. I'll

Re: [Libusbx-devel] Feature request: plug-in notification.

2013-03-13 Thread Xiaofan Chen
On Wed, Mar 13, 2013 at 5:31 PM, Bent Bisballe Nyeng wrote: > In the time I have been using libusb there has always been a single > feature that I was missing: The ability to get a notification when a new > device is connected (or disconnected for that matter), and thereby > remove the need for co

[Libusbx-devel] Feature request: plug-in notification.

2013-03-13 Thread Bent Bisballe Nyeng
Hi list I have been made aware of the libusbx project recently, and there were much rejoicing... I found many bugs (especially on windows) that were fixed compared with libusb so the choice of changeover was an easy one - thank you for that. In the time I have been using libusb there has always

Re: [Libusbx-devel] Functions needed by argyllcms

2013-03-13 Thread Xiaofan Chen
On Wed, Mar 13, 2013 at 3:07 PM, Richard Hughes wrote: > I think the main issue is that he can't actually make his driver code > work correctly without things like libusb_handle_events_check (which > makes sense to me) and also libusb_resetep (which also makes sense for > me on Linux). I am not s

Re: [Libusbx-devel] Functions needed by argyllcms

2013-03-13 Thread Richard Hughes
On 12 March 2013 22:42, Pete Batard wrote: > 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_. Sure, it was meant somewhat tongue-in-cheek, so I appreciate the response. I'm not deliberately trolling. > Ergo, the time