On Thu, Oct 16, 2014 at 02:55:22PM +0400, Victor Ashik wrote: > 16.10.2014 14:02, Johan Hovold пишет: > > 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. > > > [91798.346109] usbserial: unknown parameter 'debug' ignored The debug module parameter has been removed. You need to enable it using dynamic debugging (e.g. through debugfs). > [91798.346489] usbcore: registered new interface driver usbserial > [91798.346512] usbcore: registered new interface driver usbserial_generic > [91798.346531] usbserial: USB Serial support registered for generic > [91803.034148] ftdi_sio: unknown parameter 'debug' ignored Same here (although it seems you enabled it in the driver directly). > [91803.034572] usbcore: registered new interface driver ftdi_sio > [91803.034695] usbserial: USB Serial support registered for FTDI USB > Serial Device > [91803.034757] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected > [91803.034898] usb 1-1.2: Detected SIO > [91803.034901] usb 1-1.2: Number of endpoints 2 > [91803.034902] usb 1-1.2: Endpoint 1 MaxPacketSize 64 > [91803.034904] usb 1-1.2: Endpoint 2 MaxPacketSize 64 > [91803.034906] usb 1-1.2: Setting MaxPacketSize 64 > [91803.035940] ftdi_sio ttyUSB0: Unable to read latency timer: -32 > [91803.036435] ftdi_sio ttyUSB0: Unable to write latency timer: -32 > [91803.036711] usb 1-1.2: FTDI USB Serial Device converter now attached > to ttyUSB0 > [91806.063117] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set > databits/stopbits/parity > [91806.063467] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate > [91806.063806] ftdi_sio ttyUSB0: urb failed to clear flow control > [91806.064545] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate > [91806.064914] ftdi_sio ttyUSB0: urb failed to clear flow control > [91806.065289] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate > [91806.065662] ftdi_sio ttyUSB0: urb failed to set to rts/cts flow control > [91806.066036] ftdi_sio ttyUSB0: failed to get modem status: -32 > [91806.066414] ftdi_sio ttyUSB0: urb failed to set to rts/cts flow control > [91812.841711] ftdi_sio ttyUSB0: failed to get modem status: -32 > [91812.842077] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate > [91812.842437] ftdi_sio ttyUSB0: urb failed to clear flow control > [91812.842788] ftdi_sio ttyUSB0: failed to get modem status: -32 > [91812.843160] ftdi_sio ttyUSB0: error from flowcontrol urb So basically all control transfers are failing. (This should really have been logged at error log level -- I'll fix that up.) I'll try to have a look at the bsd logs you sent soon. Meanwhile you could test if the device works at 115200 8N1, which could be the default baud rate. Thanks, 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
