Cyclom Multi-Port Cards

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

Gert Doering wrote:
> 
> Hi,
> 
> On Wed, Nov 25, 1998 at 01:28:30AM -0600, Robert Canary wrote:
> > > setserial is NOT recommended AT ALL.  Mgetty and most other useful
> > Yes, that's pretty much what they are saying.
> 
> No, it's not.  They explicitely recommend using setserial to get 57600 and
> 115200 bps.

Not what I read, I took it as *not* neccsary -but- if you had to the
thing it is good for is to force the ttyCx port to certain speed.  Which
as you explained is useless.

>< snip ><
> 
> > function mgetty(reset_CPU_to_port_speed){
> >     case in "reset_CPU_to_port_speed"
> >       cannot)
> >           setserial /dev/ttyC0 spd_vhi
> >           msg="mgetty cannot control port to CPU speeds, using setserial"
> 
> unnecessary, as mgetty can *always* set any speed it wants.  This is what
> I keep saying:  "setserial spd_[v]hi" is not needed anymore.  Forget about
> its existance.
> 
> [..]
> > Does mgetty reset the CPU-to-port speed?  If it does then what's the
> > problem
> 
> It doesn't reset "setserial" follies, 'cause this is very much nonportable
> and I refuse to add code for it.  It *does* log a warning message if you
> have used setserial, though.

Hmmm, I am using it and I have never seen a warning message on it yet. 
At what debug level does show up in the log files. In fact I set all my
ports with setserial spd_vhi and I quit getting those pescky TIO errors
in my log files, and vgetty finally quit loosing the first 2 seconds of
ICMs. 

--
robert