Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!aplcen!samsung!cs.utexas.edu!rice!rice!sun-spots-request
From: auspex!guy@uunet.uu.net (Guy Harris)
Newsgroups: comp.sys.sun
Subject: Re: Serial port speed
Keywords: Miscellaneous
Message-ID: <1990Aug13.010259.4451@rice.edu>
Date: 9 Aug 90 20:55:59 GMT
Sender: sun-spots-request@rice.edu
Organization: Sun-Spots
Lines: 17
Approved: Sun-Spots@rice.edu
Originator: spots@titan.rice.edu
X-Sun-Spots-Digest: Volume 9, Issue 298, message 14
X-Refs:  Original: v9n264, Replies: v9n267 v9n272 v9n277 v9n292

>When I asked Guy Harris about this in '88, he couldn't think of any reason
>that you might want to set a 'nonstandard' serial port speed, and didn't
>want to change it.

Err, no, he didn't say he couldn't think of a reason why you wouldn't want
to set a 'nonstandard' serial port speed, he said that the example you
gave of a reason why you might want to do so - a MIDI port - might also
want a different line discipline and perhaps even changes in the low-level
serial port driver (does MIDI use the same character framing as an
asynchronous serial line?).

Part of the concern was with getting AT&T to buy into the interface; if
the price of getting S5R4 to have a reasonably pleasant tty driver was to
keep the way speeds were stored similar to the way S5 did them, it's a
price I have no problem paying....  I don't know that AT&T wouldn't have
bought into an interface like that, but frankly I was too fatigued to even
contemplate trying to hard to get them to do so.