From owner-freebsd-hackers  Tue Nov 12 12:57:34 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA26718
          for hackers-outgoing; Tue, 12 Nov 1996 12:57:34 -0800 (PST)
Received: from pluto.plutotech.com (root@pluto.plutotech.com [206.168.67.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA26713
          for <freebsd-hackers@freebsd.org>; Tue, 12 Nov 1996 12:57:28 -0800 (PST)
Received: from shane.plutotech.com (durian@shane.plutotech.com [206.168.67.149]) by pluto.plutotech.com (8.8.2/8.8.2) with ESMTP id NAA04343; Tue, 12 Nov 1996 13:57:10 -0700 (MST)
Message-Id: <199611122057.NAA04343@pluto.plutotech.com>
From: "Mike Durian" <durian@plutotech.com>
To: se@zpr.uni-koeln.de (Stefan Esser)
cc: freebsd-hackers@freebsd.org
Subject: Re: small bugs in pci code 
In-reply-to: Your message of "Tue, 12 Nov 1996 21:02:10 +0100."
Date: Tue, 12 Nov 1996 13:57:09 -0700
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 12 Nov 1996 21:02:10 +0100, se@zpr.uni-koeln.de (Stefan Esser) wrote:
>
>Thanks! And I think I found something interesting ...
>
>Could you please let me know the value of PCI_MAP_REG_END 
>that is defined in your version of /sys/pci/pcireg.h ?
>
>(It should be 0x28, in order to make the following for loop
>do the right thing:

  You are absolutely right.  For some reason mine was set to 0x34.
I have no explaination for this.  Either we made the change locally
(and I have no idea why), or it was in the FreeBSD source tree at
one point and we missed picking up the change during one of our
imports.

>Ok, the rest just repeated, what we already know:
>
>On your system, the probe for PCI map registers (which should be
>limited to the range 0x10 to 0x24 (+3)) does not stop when it has
>completed looking at the defined registers. And it does bad things,
>when it walks over all the higher numbered registers and writes a
>0xffffffff probe value into them !
>
>Please check why this happens on your system. I can't reprocuce it 
>here ...

  It is just as your surmised.  Thanks for your help, and sorry about
the wild goose chase.

  As for the ROM on the adaptec being enabled, I'm not sure what to do
about that.  Isn't that a BIOS issue?  I mean, shouldn't the BIOS have
disabled it?

mike