On Thu, Oct 16, 2014 at 12:47:05PM +0400, Victor Ashik wrote: > Wed, Oct 15, 2014 at 6:00 PM, Johan Hovold <johan@xxxxxxxxxx> wrote: > > No, we're still supposed to support the legacy SIO type of devices, > > although that code doesn't get much testing I'm afraid. > > > > But let's start with verifying that the type is actually detected. > > > > Could you post the kernel log from when plugging the device in along > > with the "lsusb -v" output for it? > > > [83986.455025] usb 1-1.2: New USB device found, idVendor=0403, > idProduct=8372 > [83986.455029] usb 1-1.2: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [83986.455031] usb 1-1.2: Product: USB Serial Converter > [83986.455032] usb 1-1.2: Manufacturer: FTDI > [83986.455033] usb 1-1.2: SerialNumber: FT00026B > [83986.472948] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected > [83986.472972] usb 1-1.2: Detected SIO So the type is indeed detected correctly. > [83986.472974] usb 1-1.2: Number of endpoints 2 > [83986.472975] usb 1-1.2: Endpoint 1 MaxPacketSize 64 > [83986.472976] usb 1-1.2: Endpoint 2 MaxPacketSize 64 > [83986.472977] usb 1-1.2: Setting MaxPacketSize 64 > [83986.473150] ftdi_sio ttyUSB0: Unable to read latency timer: -32 > [83986.473626] ftdi_sio ttyUSB0: Unable to write latency timer: -32 > [83986.473673] usb 1-1.2: FTDI USB Serial Device converter now attached to > ttyUSB0 Are you able to verify if rx or tx works separately, e.g. by connecting to a working serial port and setting up two terminal sessions? Remember to try with flow control disabled on both ends as well. Also could you post a log from when opening, reading/writing and closing the device? Make sure to enable debugging in usb-serial core as well. Using echo and cat (e.g. echo hello >/dev/ttyUSB0) can suffice as long the port has been properly set up. Johan -- 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
