petr@xxxxxxxxxxx writes: > OK. Do you know the protocol? Yes, it's just 2 plain raw streams of bytes, in and out, for USB driver itself. Everything else is application-dependent, as I've alredy wrote. > User space - use /proc entries. See Apogee CCD driver for an example, > or ask me, I might be able to reveal parts of MI CCD driver which does > that. > > Kernel space - see some existing (FTDI,..) drivers and write your own. No available driver that is capable to handler raw in/out bulk except "usbserial"? Well, I actually wrote one a few years ago, when usbserial was really sloooooow, but then the latter got better and I din't care to either finish or submit my own since then. But as I now learned I shouldn't use usbserial for that (and besides it looks like it's buggy in 3.2.0 that I'm running right now). -- Sergei. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
