From owner-freebsd-hackers Sun Dec 20 21:14:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05128 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 21:14:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05106 for ; Sun, 20 Dec 1998 21:13:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA49211; Sun, 20 Dec 1998 21:11:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210511.VAA49211@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PCI IRQ mappings In-reply-to: Your message of "Mon, 21 Dec 1998 13:08:55 +1030." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Dec 1998 21:11:32 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm wondering if its possible to reassign IRQ's for PCI cards. The > BIOS does the origional mapping (I think) but sometimes this is broken, > 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? > I had a look at the 440BX datasheet but I couldn't find anything > pertinent. Is it possible? Windows seems to let you do it, and I'm > curious how. 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. This is the only way to do this correctly. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message