On Sat, Oct 27, 2012 at 11:41 AM, therau2000 wrote:
> libusbx is required because my Java Program is used on Linux and Mac OS X as
> well. My prototype program does work without any modification under 64-bit
> Linux. I have not tried it under Mac OS X yet due to lack of time.
Under Mac OS X you w
On Fri, Oct 26, 2012 at 8:05 PM, Stefano Di Martino wrote:
> Here the debug log what I actived before I call
> libusb_get_string_descriptor_ascii()
>
> [timestamp] [threadID] facility level [function call]
>
> [ 0.9
On Sun, 2012-10-28 at 08:58 +0800, Xiaofan Chen wrote:
> On Sat, Oct 27, 2012 at 11:41 AM, therau2000 wrote:
> > libusbx is required because my Java Program is used on Linux and Mac OS X as
> > well. My prototype program does work without any modification under 64-bit
> > Linux. I have not tried
On Sun, Oct 28, 2012 at 11:29 AM, therau2000 wrote:
> Under Mac OS X you will have problem as well but a codeless kext may
> help in order to use libusbx. In that case, the device will not function as
> a USB mass storage device. So you have a problem there as well.
> https://github.com/texane/st
On Sun, Oct 28, 2012 at 8:58 AM, Xiaofan Chen wrote:
>
> Unfortunately libusbx is not the solution for your problem. If you have the
> control of the device firmware, you should make the device a USB composite
> device, with an interface to be the USB Mass Storage device and the other
> interface
