From: Vinzent Hoefler Newsgroups: comp.os.msdos.djgpp Subject: Re: Libnet serial port problem Date: Wed, 15 Jan 2003 09:58:14 -0500 Organization: JeLlyFish software Lines: 42 Message-ID: <6us30b.la2.ln@jellix.jlfencey.com> References: <3e23e78b$1 AT news DOT infonet DOT ee> <3e2520c5$1 AT news DOT infonet DOT ee> NNTP-Posting-Host: firewall.mdc-dayton.com (12.161.103.180) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Trace: fu-berlin.de 1042642758 22251197 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: >> > 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. > > You expect that UARTS can share IRQ-s. Yes, because I know it is possible. > I dont know, but on older machines they dont. They can. In theory, at least. > At least ISA bus IO cards dont. Sure they can, as long as all UARTs are on the same card. > So its not "Just bad software" but can > be also bad harware as most PC platform hardware is. Yes, this might be the case. > I think that this libnet is some older library and it doesnt handle > IRQ sharing also. As I said: Bad software. ;-) > Only bullet-proof solution is to not use the same IRQ or not to use > IRQ at all :[ I know. Vinzent. -- A student who changes the course of history is probably taking an exam.