From owner-freebsd-hackers Mon Jul 24 12:15:00 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id MAA05958 for hackers-outgoing; Mon, 24 Jul 1995 12:15:00 -0700 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id MAA05947 for ; Mon, 24 Jul 1995 12:14:50 -0700 Received: by sovcom.kiae.su id AA29278 (5.65.kiae-1 ); Mon, 24 Jul 1995 22:06:48 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Mon, 24 Jul 95 22:06:48 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id WAA00439; Mon, 24 Jul 1995 22:59:40 +0400 To: Bruce Evans , Terry Lambert Cc: hackers@freebsd.org, harry@hgac.com, jkh@violet.berkeley.edu References: <9507241827.AA07622@cs.weber.edu> In-Reply-To: <9507241827.AA07622@cs.weber.edu>; from Terry Lambert at Mon, 24 Jul 95 12:27:09 MDT Message-Id: Organization: Olahm Ha-Yetzirah Date: Mon, 24 Jul 1995 22:59:40 +0400 (MSD) X-Mailer: Mail/@ [v2.40 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Re: dial up at > 9600 baud Lines: 43 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1847 Sender: hackers-owner@freebsd.org Precedence: bulk In message <9507241827.AA07622@cs.weber.edu> Terry Lambert writes: >This is really my whole problem with rc.serial, which could probably >be argued for on the basis of CTS/RTS flow control, and maybe nothing >else. >It should be irrelevant what the new port speed is if the modem can't >detect it. >The current discussion is predicated on the modem being somehow able to >detect it. >The default baud being 9600 is not the problem. The modem being able >to "magically" detect the baud which the port is set to *is* the problem. >The only way to solve this thing is to find where the error is in the >driver or in the getty or in the modem cable or in the modem settings >and correct it. Terry, you seems to miss a bit of discussion: situation is pretty clear: modem inherits speed of previous access, if it isn't configured to reset by DTR drop. It means that any dialout application which change speed becomes getty-killer. There is no error in the driver or in getty. Solution for it already exists: 1) Configure modem to gettytab speed and issue AT&W. 2) Configure modem to do ATZ on DTR drop. If we allow modem to not do ATZ on DTR drop, more complex things will be involved in driver and getty, namely: 1) Driver must issue "AT" command at first open to give modem chance to sense speed. 2) driver must restore dialin speed in close and issue "AT" command to give modem chance to sense speed. 3) getty must setup initial device with gettytab speed for #1 & #2 will be successful. Doing "AT" commands in the driver not nice thing, of course. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849