Date: Sat, 14 Mar 1998 16:19:56 -0500 From: Howard Goldstein <hgoldste@bbs.mpcs.com> To: freebsd-questions@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Cc: efinley@castlenet.com, lauralyng@rocket.comtrol.com, tomm@comtrol.com Subject: Re: Rocketport DTR, 2.2.5R, mgetty - RESOLVED Message-ID: <199803142119.QAA19198@bbs.mpcs.com> In-Reply-To: <199803141730.MAA09924@bbs.mpcs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In previous episodes I wrote: : : Under 2.2.5R? comtrol's August drivers fail to diddle DTR under : 2.2.5R, and -current drivers under 2.2.5R with enough patching so : they'll build get stuck in ioctl() forever. This turned out to be woefully incorrect. More verbose logging of mgetty's activities revealed that the real culprit was mgetty's attempted use of vtime. That mgetty didn't have a problem with vtime in operating on the standard cuaa ports, and too-terse logging, conspired to lead to an erroneous conclusion about broken DTR control. Rebuilding mgetty with BROKEN_VTIME (and reassigning the August comtrol driver's idea of major device #s to the one assigned in -current (i.e., 81), but this reassigment might not have been necessary under 2.2.5R...) fixed the problem. To the folks on the Cc: list, thank you for your advice and comments. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803142119.QAA19198>