On Thu, Oct 16, 2014 at 02:21:02PM +0200, Johan Hovold wrote:
> 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:
> > [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.)
They are logged at error level. You just haven't enabled debugging yet.
> 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.
Could you try the patch below? It's a bit of a long shot, but if it
works this bug predates the shift to git in 2005. :)
If it does not work, could you provide a log from when opening the
device on netBSD with debugging enabled in that driver?
Thanks,
Johan
>From 95b16d865f629587b0d10a01e168c4f1641af67a Mon Sep 17 00:00:00 2001
From: Johan Hovold <johan@xxxxxxxxxx>
Date: Wed, 29 Oct 2014 17:59:19 +0100
Subject: [PATCH] USB: ftdi_sio: fix legacy SIO interface number
Signed-off-by: Johan Hovold <johan@xxxxxxxxxx>
---
drivers/usb/serial/ftdi_sio.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
index dc72b924c399..56adc06b4e2e 100644
--- a/drivers/usb/serial/ftdi_sio.c
+++ b/drivers/usb/serial/ftdi_sio.c
@@ -1531,6 +1531,7 @@ static void ftdi_determine_type(struct usb_serial_port *port)
/* Old device. Assume it's the original SIO. */
priv->chip_type = SIO;
priv->baud_base = 12000000 / 16;
+ priv->interface = PIT_SIOA;
} else if (version < 0x400) {
/* Assume it's an FT8U232AM (or FT8U245AM) */
/* (It might be a BM because of the iSerialNumber bug,
--
2.0.4
--
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
