> It shouldn't. Your device follows the CDC ACM specification, aside from > the incorrect subclass. Such devices don't generate /dev/ttyUSB devices > nodes. They generate /dev/ttyACM nodes. > Thank you. I did some more research on this last night and found out that I was being mis-lead by observing how other USB Serial devices were working and used under Linux - without having to install a driver. Apparently these were all using the FTDI chip - and there is a driver that is already installed for them. > That is the wrong driver. usbserial is for vendor specific serial devices. > Your device follows a class specification. You need cdc_acm. As soon > as the subclass is fixed, it should autoload. > Yes - the driver now autoloads and I can communicate with the device using the /dev/ttyACM0 node. I was able to install picocom and talk to and from our display. Thanks to everyone who replied to this question for your assistance. Steven J. Ackerman, Consultant ACS, Sarasota, FL http://www.acscontrol.com mailto:steve@xxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
