Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP
id AA7093 ; Mon, 18 Jan 93 10:47:20 EST
Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!gatech!usenet.ins.cwru.edu!agate!agate.berkeley.edu!cgd
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] Fix CARRIER for cgd driver, probably for standard too
Date: 18 Jan 93 04:23:50
Organization: Kernel Hackers 'r' Us
Lines: 40
Message-ID: <CGD.93Jan18042350@eden.CS.Berkeley.EDU>
References: <YI-p3KhW50@astral.msk.su>
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: ache@astral.msk.su's message of 10 Jan 93 15:13:02 GMT
(sorry it took so long to respond to this; i've been sick and drowning
and work, and trying to get ready for usenix... <chuckle)
In article <YI-p3KhW50@astral.msk.su> ache@astral.msk.su (Andrew A. Chernov, Black Mage) writes:
>This patch fix two problems with carrier control.
>
>1) User can't type anything to modem (can't redial, f.e.)
>after dropping carrier in dialout programs (pcomm f.e.)
this is *NOT* a bug. basically, when carrier is lost, the tty
(well, actually, the serial port) is supposed to be more or
less revoked. if you don't want this, use "stty clocal",
and with the fix for (2), it should behave appropriately.
>2) TIOCMGET don't report carrier status, so application
>(BinkleyTerm f.e.) can't determine carrier.
this is a real bug.
....
i'm working on a new version of my much-mangled serial driver,
w/ a slightly different (and more intelligent) lineage than
the previous...
this time i'm even going comment my changes... 8-)
if it doesn't hit the "airwaves" before wednesday, it'll be on hold
until after usenix...
later,
chris
--
Chris G. Demetriou cgd@cs.berkeley.edu
"Sometimes it is better to have twenty million instructions by
Friday than twenty million instructions per second." -- Wes Clark