From owner-cvs-all  Wed Jul 22 21:47:17 1998
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA07818
          for cvs-all-outgoing; Wed, 22 Jul 1998 21:47:17 -0700 (PDT)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07784;
          Wed, 22 Jul 1998 21:47:05 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA12452;
	Thu, 23 Jul 1998 14:46:32 +1000
Date: Thu, 23 Jul 1998 14:46:32 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199807230446.OAA12452@godzilla.zeta.org.au>
To: brian@Awfulhak.org, phk@critter.freebsd.dk
Subject: Re: cvs commit: src/etc gettytab
Cc: cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-etc@FreeBSD.ORG
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

>>>   Modified files:
>>>     etc                  gettytab 
>>>   Log:
>>>   Add std.230400 entry

>>How does this work at the UART level then ?  I thought the lowest 
>>value that can be put in the divisor port is 1 (== 115200).  Do 16550 
>>UARTS have the ability to understand 0 or something ?
>
>Who said it would work with any specific hardware ?
>
>It allows you to instruct hardware that can do 230400 to do so.

It's fundamentally wrong, since it doesn't allow you to instruct harware
that can do 230401 to do so; supporting all the settings would require
2^64-2 entries in gettytab on alpha (only 2^31-2 on i386).

More practically, 230400 is not supported by the sgtty emulation, and
several tables of speeds, e.g. speeds[] in rlogin.c, end at 115200.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message