From owner-freebsd-hackers Sun Sep 28 02:22:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA21451 for hackers-outgoing; Sun, 28 Sep 1997 02:22:49 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA21420 for ; Sun, 28 Sep 1997 02:22:33 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id SAA05487; Sun, 28 Sep 1997 18:49:00 +0930 (CST) Message-Id: <199709280919.SAA05487@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tony Overfield cc: Terry Lambert , hackers@freebsd.org Subject: Re: INB question In-reply-to: Your message of "Sat, 27 Sep 1997 05:55:43 EST." <3.0.2.32.19970927055543.006bd29c@bugs.us.dell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Sep 1997 18:48:57 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > At 02:44 PM 9/19/97 +0000, Terry Lambert wrote: > >> > 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. > > Port 0x18, on many systems, is an alias of port 0x08, which is > the read-only DMA status register and the write-only DMA command > register. Likewise, port 0x1A is often an alias of the write-only > port 0x0A DMA mask register. Eep. That's not so good then. Now you're back; do *you* know how to identify an MCA machine uniquely? mike