🚀 go-pugleaf

In article <1991Jan27.034726.15865@meadow.uucp> py@meadow.UUCP (Peter Yeung) writes:
>In article <1991Jan25.054228.157@frey.newcsatle.edu.au> kaos@frey.newcsatle.edu.au (Iain `Kaos' Holmes) writes:
>>
>>	cause i can write to the ports and they react but i think the interupts
>>
>>	are screwy...
>>
>
>Which interrupt are you using? Since the original PC does not have provision
>for com3/4, the interrupt to be used is implementation dependent.
>Most implementations chose to share the interrupts with those being used
>by com1/2. Also, typically, those async cards supporting com3/4 also allow
>the user to choose the interrupt/port address etc. So, make sure you are
>catching the interrupt same as the one setup on the card!
>

COM3 & COM4 have defined, standard addresses and IRQ settings. 
	COM3 Uses a base address for the UART at 3E8 and IRQ 4
	COM4 Uses a base address for the UART at 2E8 and IRQ 3

The interesting thing is that if you are using interrupt driven communications
on, say, COM1 and COM3, you will need to determine the source of the interrupt
based on the IID register on both UARTS. I don't know what happens if 
interrupts happen simultaneously.

Hope this helps,
Steve



-- 
-------------------------------------------------------------------------------
resnicks@netcom.com, apple!camphq!105!steve.resnick, IFNA:	1:143/105.0, 
USNail: 530 Lawrence Expressway, Suite 374 
        Sunnyvale, Ca 94086
- In real life: Steve Resnick. Flames, grammar and spelling errors >/dev/null
0x2b |~ 0x2b, THAT is the question.
-------------------------------------------------------------------------------