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...? Message-ID: <19971003104948.15501@mi.uni-koeln.de> In-Reply-To: <199710021848.VAA31187@dol-guldur.hut.fi>; from Ville-Pertti Keinonen on Thu, Oct 02, 1997 at 09:48:47PM %2B0300 References: <199709281110.OAA04780@dol-guldur.hut.fi> <19970929084523.37780@mi.uni-koeln.de> <199710021848.VAA31187@dol-guldur.hut.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971003104948.15501>