From owner-freebsd-chat Thu May 3 11: 3:45 2001 Delivered-To: freebsd-chat@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id E341B37B422 for ; Thu, 3 May 2001 11:03:39 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.3/8.11.3) with ESMTP id f43I3Gp71344; Thu, 3 May 2001 20:03:20 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200105031803.f43I3Gp71344@gratis.grondar.za> To: Brett Glass Cc: chat@FreeBSD.ORG (chat@FreeBSD.ORG) Subject: Re: Modem Woes References: <4.3.2.7.2.20010503114324.0459d260@localhost> In-Reply-To: <4.3.2.7.2.20010503114324.0459d260@localhost> ; from Brett Glass "Thu, 03 May 2001 11:49:37 CST." Date: Thu, 03 May 2001 20:05:09 +0200 From: Mark Murray Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >In FreeBSD, COM ports can not share IRQs. > > Terry, this is not correct. I have several multiport cards > in which several UARTs share IRQs. They all run fine > under FreeBSD. Here's an excerpt from the kernel config of > one of them: Erm you guys are talking about different things. COMports are the "usual" serial ports that one finds on the motherboard these days and on a "multi-io" card in the old days. > device sio2 at isa? port "IO_COM3" tty flags 0x585 vector siointr > device sio3 at isa? port "IO_COM4" tty flags 0x585 vector siointr > device sio4 at isa? port 0x1f8 tty flags 0x585 vector siointr > device sio5 at isa? port 0x1e8 tty flags 0x585 irq 9 vector siointr These are mutiport cards, and they can share interrupts _only_ because they have the hardware to do it. This hardware is NOT usual on a "normal" COMport. M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message