Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pacbell!att!mcdchg!ddsw1!tronsbox!tron1
From: tron1@tronsbox.UUCP (HIM)
Newsgroups: comp.unix.i386
Subject: YASPP (Yet another serial port problem)
Message-ID: <259eaa86:553.1comp.unix.i386;1@tronsbox.UUCP>
Date: 1 Jan 90 01:11:49 GMT
References: <10740@attctc.Dallas.TX.US>
Lines: 35

>Item: 553 by *Masked* at attctc.Dallas.TX.US
>Author: [Cassidy Lynar]
>  Subj: YASPP (Yet another serial port problem)
>  Keyw: 
>  Date: Sun Dec 31 1989 09:17 EST
>asy 	Y	1	7	1	4	3f8 	3ff	0	0
>asy	Y	1	7	1	3	2f8	2ff	0	0
>asy	Y	1	7	1	5	3e8	3ef	0	0
>allow to PHYSICALLY change the addresses from 3f8 to 3e8 and the irq from
>4 to 5. I also tried to as ISC put it, "fake the kconfig" and modified the
>....
>fine, but the probs are 1) the getty process becomes a non-killable process

Oh , but this happens to some us us ANYWAY !!!! (grin)
there are some things to try , like (for one) doing a (as root) >/dev/foo
where foo is the DIAL OUT device name of that port.

>			2) when I cat foo >> /dev/tty02, the terminal on the
>other end, receives the data at a smoking 1 cps or less. I know that the

SOunds like an interrupt conflict with another driver/device. Try running it
on a shared interrup with another port , this should not be a problem.
I say this because many dumb cards have one interrupt for 4-5 ports.

Alternate driver is being emailed anyway.

****************************************************************************
"Perfume and leather baby , you and me together baby,
  what good is living in paradise, if you don't let yourself once or twice."
 -Tiffany  
 
 Kenneth J. Jamieson ---- THE BOSS at Xanadu Enterprises Inc.
      UUCP: tron1@tronsbox.UUCP  BEST PATH ---> uunet!tronsbox!tron1 
      Sysop, Romantic Encounters BBS - (201)759-8450 / (201)759-8568 
****************************************************************************