From:	Andrew Cottrell <andnews AT ihug DOT com DOT oz DOT au>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Determining interrupt vector for serial port
Date:	Thu, 06 Feb 2003 23:00:06 +1100
Organization:	ECLiPSE
Lines:	17
Message-ID:	<osi44v4fu7h6ctc1mpq2f6b8pg5bcb5sdh@4ax.com>
References:	<b1qcar$16070j$1 AT ID-83062 DOT news DOT dfncis DOT de>
NNTP-Posting-Host:	p126-tnt7.syd.ihug.com.au
Mime-Version:	1.0
X-Trace:	lust.ihug.co.nz 1044532807 13393 203.173.144.126 (6 Feb 2003 12:00:07 GMT)
X-Complaints-To:	abuse AT ihug DOT co DOT nz
NNTP-Posting-Date:	Thu, 6 Feb 2003 12:00:07 +0000 (UTC)
X-Newsreader:	Forte Agent 1.92/32.572
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

>But I've been unable to discover how to "read" the associated IRQ
>value for each port.  So far I've found them hardcoded as 4, 3,
>4, 3 respectively in all examples.  But I've got to look no
>further than my own PC to find COM3 using IRQ5 (on an ISA card).
>How does a program discover this?
>
>In the interests of robust software, is someone able to help me
>move forwards here?
I had a look at PMCOM and DZCOMM source and they don't detect the irq.
I had a look at one of the serial docs I download from the web and it
has a C program on how to do it.

Search google for the following and you will find the serial port doc
release 19 on a number of sites:-
Christian Blum The serial port release 20

Andrew

- Raw text -