From owner-cvs-sys  Sun Aug 31 12:41:40 1997
Return-Path: <owner-cvs-sys>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id MAA15020
          for cvs-sys-outgoing; Sun, 31 Aug 1997 12:41:40 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA14876;
          Sun, 31 Aug 1997 12:37:24 -0700 (PDT)
From: Stefan Esser <se@FreeBSD.ORG>
Received: (from se@localhost)
	by freefall.freebsd.org (8.8.6/8.8.5) id MAA25250;
	Sun, 31 Aug 1997 12:35:54 -0700 (PDT)
Date: Sun, 31 Aug 1997 12:35:54 -0700 (PDT)
Message-Id: <199708311935.MAA25250@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-sys@FreeBSD.ORG
Subject: cvs commit: src/sys/pci ncr.c
Sender: owner-cvs-sys@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

se          1997/08/31 12:35:54 PDT

  Modified files:
    sys/pci              ncr.c 
  Log:
  Fix problem with early revision 53c825a and 53c875 chips, which
  could cause a solid system lockup in the driver attach:
  
  These chips do not abort an access to the internal SRAM, when
  the driver set the software reset bit in the istat register. But
  the chip will never acknowledge the requested PCI bus transfer
  in the situation, causing an infinite wait and a lockout of other
  bus-masters.
  
  The problem has been reported for rev 0x11 of the 53c825a and
  rev 0x01 of the 53c875.
  Revisions 0x13 of the 53c825a and 0x03 of the 53c875 are known
  to support SRAM accesses, even in the software reset state.
  
  Revision  Changes    Path
  1.106     +3 -5      src/sys/pci/ncr.c