On Wed, Mar 3, 2010 at 3:06 AM, Greg KH <greg@xxxxxxxxx> wrote: > On Mon, Mar 01, 2010 at 01:15:54PM +0300, Dave Milter wrote: >> Hi, >> >> I have device, that implement Communication Device Class. >> And want to connect it to my machine. On Windows give system proper >> inf file with >> vendor and product id, I was abble to communicate with device using >> virtual com port and hyperterminal. >> >> Now I want to use it on linux. But the problem is that there are >> already several devices connected to my machine, >> that use usbserial indirectly. >> >> If I remove pl2303,ftdi_sio,usbserial, then run >> insmod usbserial vendor= product= > > Ick, never do that. You NEVER want to add a new device id to the > usbserial core, if you ever see anyone suggest you do that, it is flat > out wrong. > >> All ok: >> >> usbserial_generic 4-2:1.1: generic converter detected >> usb 4-2: generic converter now attached to ttyUSB0 >> usbcore: registered new interface driver usbserial_generic >> usbserial: USB Serial Driver core >> >> but when other devices connected, I type >> modprobe usbserial vendor= product=, >> and nothing happened. >> >> So question, how can I use usbserial generic, if I already load and work with: >> pl2303 and ftdi_sio? > > As your device uses the cdc spec, why are you trying to use the > usbserial core for it? What is wrong with the existing cdc_acm driver? > > confused, Because of I never hear about cdc_acm driver, instruction which come with device suggest use "modprobe usbserial vendor" trick. I will try cdc_acm, thanks. -- 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
