Yes, that's another option, thanks We just have to evaluate what kind of performance would that offer to us. And of course change it to bash, as we dont have any TCL

Thanks again Josh! It's really nice to have someone to support his project so much and so well!!

Josh wrote:Fortunately, you don't have to guess ...

Take the lowest ttyUSB port (interface) that includes an endpoint with "Interrupt" type. You can check this in the device tree (under "/sys/bus/usb/devices").

That's really helpful! Thanks a lot!

Hi Josh,

I'm sorry if I didn't explain myself better...

When I am talking about the database, Im talking about the configPack.tar.gz file and its included files (after all a database is just a collection of data in an organized form ;) ).

In its original form, its size is:

12K configPack.tar.gz ...

The included database of devices is almost 1MiB in size when uncompressed. For those of you working on embedded devices what kind of strategy are you following to store that information in your device? 1MiB can be a lot for some kind of devices.

Do you know of a way to make usb_modeswitch to work ...

Good Morning everyone,

I have ported usb_modeswitch for my embedded platform. We don't use udev at all, so we usually run usb_modeswitch when we detect a new usb device connected to the system with the vendor and prod id.

$ usb_modeswitch -c 19d2\:1013


But then we have the problem of multiple ...

Thanks, it turns out I was having problems with libusb-compat. After going to an old libusb version it worked.

Hello everyone there :)

I am trying to compile usb/modeswitch for a MIPS board. Is there any kind of requirements to make it work?

My kernel is 2.6.22.15 and gcc is 4.3.4. I already cross-compiled libusb without problems. But Im getting errors when doing so for usb_modeswitch

$ mips-linux-gcc -o ...