Path: utzoo!attcan!uunet!dino!ux1.cso.uiuc.edu!uwm.edu!zaphod.mps.ohio-state.edu!van-bc!sl From: sl@van-bc.UUCP (Stuart Lynne) Newsgroups: comp.unix.xenix Subject: Re: COM3 & COM4 under SCO Xenix ? Keywords: xenix com serial Message-ID: <269@van-bc.UUCP> Date: 21 Mar 90 20:59:03 GMT References: <3347@trantor.harris-atd.com> <5275@scolex.sco.COM> <683@sixhub.UUCP> Reply-To: sl@van-bc.UUCP (Stuart Lynne) Distribution: na Organization: Wimsey Associates Lines: 47 In article <683@sixhub.UUCP> davidsen@sixhub.UUCP (bill davidsen) writes: >In article <5275@scolex.sco.COM> md@sco.COM (Michael Davidson) writes: > >| Now, consider the situation where COM1 has just interrupted on line >| 3 causing the line to change from the inactive to the active state. >| The interrupt controller sees the transition and latches the interrupt. >| Suppose that COM3 then attempts to interrupt on the same line >| *before* the line has returned to it's inactive state - the line is >| already active so you can't get an inactive -> active transition, >| there is no transition for the interrupt controller to see and >| you lose the interrupt. > > What you say is true, but you can get by it with a little clever >programming which polls the status of both uarts and servicea all >devices which have tbe or rda set. This is how some multiport cards >support use of a single interrupt. > Something like the following is required to support multiple 8250 type devices on a single interrupt. #define MAXDEV ? int notfinished; int devno; do { notfinished = 0; for (devno = 0; devno