From owner-freebsd-hackers Fri Sep 19 07:51:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA16461 for hackers-outgoing; Fri, 19 Sep 1997 07:51:31 -0700 (PDT) Received: from usr07.primenet.com (tlambert@usr07.primenet.com [206.165.6.207]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA16442 for ; Fri, 19 Sep 1997 07:51:28 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id HAA06050; Fri, 19 Sep 1997 07:44:27 -0700 (MST) From: Terry Lambert Message-Id: <199709191444.HAA06050@usr07.primenet.com> Subject: Re: INB question To: mike@smith.net.au (Mike Smith) Date: Fri, 19 Sep 1997 14:44:27 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, sos@sos.freebsd.dk, hackers@FreeBSD.ORG In-Reply-To: <199709190659.QAA01136@word.smith.net.au> from "Mike Smith" at Sep 19, 97 04:29:02 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This isn't the MCA configuration information; this is the BIOS > hardware table. I mean the soft configuration information that you > mung with the config disk. I have no idea where that lives; I haven't even gotten around to building an EISA config under UNIX (I at least know where that data lives, and the format of the .INF files). I doubt you will be able to get rid of the DOS configuration tool for MCA any time soon. > > Yeah; that's why I picked the extended MCA DMA ports for the detect; > > that, and I can do the probe non-destructively, with the expectation of > > a 0 bit in my data and no hardware configuratio changes resulting. > > Where is the port exactly? ie. is it likely to be sat on or masked > over by an ISA device? Port 0x18 is the control, and port 0x1A is the data. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.