From owner-freebsd-hackers Sun Dec 20 21:31:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06989 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 21:31:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06984 for ; Sun, 20 Dec 1998 21:31:46 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id QAA24122; Mon, 21 Dec 1998 16:01:42 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812210521.VAA49288@dingo.cdrom.com> Date: Mon, 21 Dec 1998 16:04:18 +1030 (CST) From: "Daniel O'Connor" To: Mike Smith Subject: Re: PCI IRQ mappings Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Dec-98 Mike Smith wrote: > > > Can you define "broken" in a useful fashion? > > Doesn't work/crashes machine. The network cards don't appear to like sharing IRQ's :( > > (Although its a little hard to say what causes it) > Bleagh. Our IRQ sharing is supposed to work; is this a hardware-level > problem (does it work under Windows)? I know and no :( It works but you have to be careful around it :-/ (ie that it gets its own IRQ) > > I see.. I thought it was device independat (ie based on the PCI chipset) > That's device dependant, and yes, it is, which is why you have to use > the BIOS (or have drivers for every motherboard chipset in the OS, > which would suck). (I should have pointed out that there are different > interrupt vectors for PCI 2.1-compliant functions.) Doh! :( Thats sucks :-/ > It sounds to me like you have a BIOS misconfiguration or bug there; if > the crash happens under "other" operating systems (eg. NT, which is > more like us in that I think it trusts the BIOS to get it right) then > you might be able to get an update out of the board vendor. Hmm.. OK.. well, we don't have NT :) (thankfully ;) I don't have a proper problem description, so I was just curious if it was possible :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message