From owner-freebsd-hardware Tue Feb 4 09:33:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA00268 for hardware-outgoing; Tue, 4 Feb 1997 09:33:07 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA00230; Tue, 4 Feb 1997 09:32:46 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA28032; Tue, 4 Feb 1997 10:32:33 -0700 (MST) Date: Tue, 4 Feb 1997 10:32:33 -0700 (MST) Message-Id: <199702041732.KAA28032@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Brett_Glass@infoworld.com Cc: Michael Smith , se@freebsd.org, Andre.Albsmeier@mchp.siemens.de, freebsd-hardware@freebsd.org Subject: Re: 5 devices in 4 PCI Slots ? In-Reply-To: <9701048550.AA855073547@ccgate.infoworld.com> References: <9701048550.AA855073547@ccgate.infoworld.com> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Interrupt sharing is a bus, not driver, issue. > > It's a driver issue as well. Last time I asked, I was told by one of your > driver developers that the current 3Com Ethernet and serial drivers were > not written so as to allow them to share an IRQ -- even though the PC card > (in this case, the 3Com Modem+Ethernet) hardware is built to do it. The 'bus' code is not setup to share the IRQ, but the drivers themselves need not be aware of it, since they don't service the interrupts directly. Nate