On Tue, Aug 20, 2013 at 9:15 PM, Toby Gray <toby.g...@realvnc.com> wrote:
> On 20/08/13 05:44, Anton Smirnov wrote:
> While usb_device_set_open_close_func(..) is clearly suitable for the
> librtlsdr-android project, I would feel that it isn't suitable as an API for
> addition to libusb. I'm not a maintainer of libusb so my opinion isn't
> important, but I would send strongly worded emails about it :)
>
> In my mind the correct solution would be to add an Android backend which
> invoked the appropriate APIs via JNI. In fact I've now added that to my TODO
> list as it'll be an interesting thing to look into, but that probably means
> many years before I actually get around to it!

That would certainly be an interesting thing to do. On the other hand,
maybe Google will change Android's USB host support down the
load that things will be very different in the future.

> Does libftdi support CDC-devices? Or have you written your own code which
> calls libusb APIs to talk to CDC-devices?

libftdi does not support CDC device. It only works with FTDI's device.
And yes libftdi depends on libusb.
   http://www.intra2net.com/en/developer/libftdi/

-- 
Xiaofan

------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel

Reply via email to