From:	Vinzent Hoefler <JeLlyFish DOT software AT gmx DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Libnet serial port problem
Date:	Tue, 14 Jan 2003 08:46:59 -0500
Organization:	JeLlyFish software
Lines:	21
Message-ID:	<kc410b.4u.ln@jellix.jlfencey.com>
References:	<f1a1bbde DOT 0301132122 DOT 7672b79f AT posting DOT google DOT com> <3e23e78b$1 AT news DOT infonet DOT ee>
NNTP-Posting-Host:	firewall.mdc-dayton.com (12.161.103.180)
Mime-Version:	1.0
X-Trace:	fu-berlin.de 1042554146 21602175 12.161.103.180 (16 [175126])
X-Orig-Path:	jellix.jlfencey.com!nobody
X-Newsreader:	KCNews v0.19b (CAOS 4.1)
X-Phone:	+1-937-271-7158
X-Homepage:	http://jlfencey.com
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Tonu Aas wrote:

>> I'm having some trouble with some serial port code I'm writing with
>> Libnet under djgpp. Everything's fine if I only use one serial port,
>> but if I try to receive from both serial ports at once, information
>> can only get through from one of them at a time. Each serial port
>> works fine by itself.
> 
> If they use the same IRQ(COM1, COM3 or COM2 COM4) then its normal.

No. Just bad software. There are enough status bits on the UART chip to 
see which one has raised the interrupt. It just slows down a little 
bite, because you have to ask all possible UART that are sharing the 
same IRQ.


Vinzent.

-- 
According to Kentucky state law, every person must take a bath at least
once a year.

- Raw text -