From owner-freebsd-hackers  Mon Nov 11 14:05:25 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA13804
          for hackers-outgoing; Mon, 11 Nov 1996 14:05:25 -0800 (PST)
Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA13771
          for <freebsd-hackers@freebsd.org>; Mon, 11 Nov 1996 14:05:10 -0800 (PST)
Received: from x14.mi.uni-koeln.de (annexr2-46.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA17770
  (5.67b/IDA-1.5 for <freebsd-hackers@freebsd.org>); Mon, 11 Nov 1996 23:04:34 +0100
Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.2/8.6.9) id XAA02428; Mon, 11 Nov 1996 23:04:38 +0100 (MET)
Message-Id: <199611112204.XAA02428@x14.mi.uni-koeln.de>
Date: Mon, 11 Nov 1996 23:04:38 +0100
From: se@zpr.uni-koeln.de (Stefan Esser)
To: durian@plutotech.com (Mike Durian)
Cc: se@zpr.uni-koeln.de (Stefan Esser), freebsd-hackers@freebsd.org
Subject: Re: small bugs in pci code
In-Reply-To: <199611111735.KAA28562@pluto.plutotech.com>; from Mike Durian on Nov 11, 1996 10:35:29 -0700
References: <199611111735.KAA28562@pluto.plutotech.com>
X-Mailer: Mutt 0.45
Mime-Version: 1.0
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Mike Durian writes:
> On Mon, 11 Nov 1996 00:10:20 +0100, se@zpr.uni-koeln.de (Stefan Esser) wrote:
> 
> >Well, I can only agree to half of that sentence: The mapping type is 
> >found in the address, but also in the size. The low bits of the map 
> >registers are hardwired. For that reason, (data & 7) is guaranteed 
> >to be identical to (map & 7) ...
> 
>   I'm not seeing this.  I'm enclosing some output from a boot on my
> machine (not the one will all the PCI busses).  I've added printfs
> to show the value of map, data and the addr, size parameters in each
> of the two cases.  As you can see (as in the ahc device), there are
> cases where the lower nybble differs in the map and data variables.
> You can also see where a memory region gets treated as an io region.
> I'm still not sure about the strange 0x500a1011 io address found on
> the DEC ethernet cards.

Well, the PCI probe in your boot message logs looks different
from everything I've seen before :-)

Please boot the same kernel (with your debug printf()s) again,
but this time with the "-v" option at the "Boot: " prompt.
This will enable even more messages about the PCI maps, and I
hope to understand from them what's going on ...
For now I'm very surprised about the behaviour of those DEC 
LAN chips ...

Thanks in advance,

STefan