From owner-freebsd-hackers Sun Dec 20 21:18:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05509 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 21:18:24 -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 VAA05504 for ; Sun, 20 Dec 1998 21:18:20 -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 PAA24039; Mon, 21 Dec 1998 15:48:15 +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: <199812210511.VAA49211@dingo.cdrom.com> Date: Mon, 21 Dec 1998 15:50:51 +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: > > so the only way to change IRQ's is to shuffle cards in the machine. Is > > there a better way? :) > 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) > Windows 9[58] take it upon themselves to manage resource allocation, > and they do this using int 1a functions 0xb10e and 0xb10f (get IRQ > routing information, set PCI IRQ). You also have to update the config > register on the PCI device. I see.. I thought it was device independat (ie based on the PCI chipset) This is a VM86 thing then? :) --- 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