From owner-freebsd-hackers  Fri Oct  3 06:31:09 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id GAA13404
          for hackers-outgoing; Fri, 3 Oct 1997 06:31:09 -0700 (PDT)
Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id GAA13398
          for <freebsd-hackers@freebsd.org>; Fri, 3 Oct 1997 06:31:06 -0700 (PDT)
Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA28424
  (5.67b/IDA-1.5 for <freebsd-hackers@freebsd.org>); Fri, 3 Oct 1997 15:31:02 +0200
Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.7/8.6.9) id KAA01014; Fri, 3 Oct 1997 10:49:48 +0200 (CEST)
X-Face: "<d]#=8pzx);RzeqSKI86OVa7=!0/(uRa.+B.9Z9\eNUn@UG?!`y7yt2dFNn%k4'.}](uE%
 yCO)$e&Y1%3EO~ifu6Q-#YUM&JZ't,}JkPnAz,8Dj33u%@GBi%[Y#LHz$]h7a<p4)-jKI7~sKjlP-^
 EvA[G;]v&0]W!EL%shs,{7x0|oqN4YVIs5,NI#,V{9"WF):5&RkOhyj*#-IAG}Tnu;YCF,d
Message-Id: <19971003104948.15501@mi.uni-koeln.de>
Date: Fri, 3 Oct 1997 10:49:48 +0200
From: Stefan Esser <se@FreeBSD.ORG>
To: will@iki.fi
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Conflicting I/O address spaces -- caused by...?
References: <199709281110.OAA04780@dol-guldur.hut.fi> <19970929084523.37780@mi.uni-koeln.de> <199710021848.VAA31187@dol-guldur.hut.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.84
In-Reply-To: <199710021848.VAA31187@dol-guldur.hut.fi>; from Ville-Pertti Keinonen on Thu, Oct 02, 1997 at 09:48:47PM +0300
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On 1997-10-02 21:48 +0300, Ville-Pertti Keinonen <will@cc.hut.fi> wrote:
> > I think your PCI BIOS is at fault. When the PC
> 
> Thanks.  That was the problem, upgrading the BIOS helped.  As a bonus,

Good!

> > Using memory accesses to the Adaptec cards is a
> > valid fix, though!
> 
> Wouldn't they still see the I/O ports, as well?

You can clear the LSB of the command register (the
config space register at offset 0x04) to prevent 
the decoding of port accesses by some device ...

> > Port addresses in PCI are only present for legacy
> > device emulations, and for DOS which has no easy
> > way to access memory mapped registers above 1MB.
> 
> That doesn't mean they shouldn't be assigned sane,
> non-conflicting values.  ;--)

Sure!

> > a fix. Using memory mapped accesses through that
> > PCI bridge may cause system hangs, but only if one
> > of several possible scenarios exists on your system.
> > They cause dead-lock, or even delivery of wrong data,
> > with a very low probability.
> 
> It seemed to always hang within less than a minute while accessing a
> SCSI disk when I had it enabled...

This was with the old PCI BIOS ?

Since accesses to the S3 card will no longer be seen by 
the Adaptec, now that it got reasonable port addresses,
it should work a lot better now :)

Regards, STefan