Date: Fri, 27 Jun 97 10:31:53 -0700 From: "Mike Burgett" <mburgett@cmnsens.zoom.com> To: "Bruce Evans" <bde@zeta.org.au> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: com console, and h/w flow control... Message-ID: <199706271731.KAA00654@dragon.cmnsens.zoom.com>
next in thread | raw e-mail | index | archive | help
On Sat, 28 Jun 1997 03:20:24 +1000, Bruce Evans wrote:
>Apparently /dev/ttyid0 never gets used because /dev/ttyd0 never gets
>reopened (init opens it before executing /etc/rc, and syslogd holds
>it open). The state is easy to change by stty'ing /dev/ttyd0 in
>/etc/rc.serial or /etc/rc.local.
I've done that (at least I think I have... rc.serial is a strange beast to
me...)
terminal() {
ci=$1; shift
co=$1; shift
modem $ci $co $*
for i in $*
do
comcontrol /dev/tty$ci$i dtrwait 0
stty </dev/ttyi$ci$i crtscts 115200
stty </dev/cuai$co$i crtscts 115200
done
}
[ .... ]
# Initialize assorted 8250-16550 (sio) ports.
modem d a 1
terminal d a 0
>crtscts is not the default, and clocal _is_ the default, to prevent
>processes endless waits for console output. clocal is locked on.
>-current also locks the speed. Perhaps crtscts should be locked
>(off) too. Then stty'ing /dev/ttyd0 would be harder :-).
Seems hard enough to me already :) ... I keep a terminal emulater window open
on another computer on the console at all times anyway, so I'd really like to
be able to get around the flow control issue...
Thanks,
Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199706271731.KAA00654>