Hallo,
I'm now looking more carefully into your baudrate patch.
I assume that you have the following device:
http://www.sitecom.com/ShowProduct.asp?PID=242
This device comes indeed with almost the same driver
(USB2SER2.3a.zip) as "my" MCT U-232 ... which puzzles
me even more.
I think it's very unlikely, that the converter works
at all with an invalid baudrate setting and a few
people out there have already used a Sitecom converter
successfully with the MCT driver (as far as I know).
Hmm, what's wrong? Could you show me a listing of the
device properties (as found in /var/log/messages or
produced with lsusb -vv).
-- Wolfgang.
PS: BTW: I know a problem with DTR/RTS setting. RTS is
not always set for hardware flow control. Here's
the patch:
# diff -u mct_u232.c.ORG mct_u232.c
--- mct_u232.c.ORG Mon Apr 16 21:30:13 2001
+++ mct_u232.c Tue May 8 21:58:06 2001
@@ -645,11 +645,7 @@
/* reassert DTR and (maybe) RTS on transition from B0 */
if( (old_cflag & CBAUD) == B0 ) {
dbg(__FUNCTION__ ": baud was B0");
- priv->control_state |= TIOCM_DTR;
- /* don't set RTS if using hardware flow control */
- if (!(old_cflag & CRTSCTS)) {
- priv->control_state |= TIOCM_RTS;
- }
+ priv->control_state |= TIOCM_DTR | TIOCM_RTS;
mct_u232_set_modem_ctrl(serial, priv->control_state);
}
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
