From owner-cvs-src@FreeBSD.ORG  Tue Apr 13 12:31:58 2004
Return-Path: <owner-cvs-src@FreeBSD.ORG>
Delivered-To: cvs-src@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 098FA16A4CE; Tue, 13 Apr 2004 12:31:58 -0700 (PDT)
Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0575343D1F; Tue, 13 Apr 2004 12:31:58 -0700 (PDT)
	(envelope-from imp@FreeBSD.org)
Received: from repoman.freebsd.org (localhost [127.0.0.1])
	by repoman.freebsd.org (8.12.10/8.12.10) with ESMTP id i3DJVvGe081520;
	Tue, 13 Apr 2004 12:31:57 -0700 (PDT)
	(envelope-from imp@repoman.freebsd.org)
Received: (from imp@localhost)
	by repoman.freebsd.org (8.12.10/8.12.10/Submit) id i3DJVvf4081519;
	Tue, 13 Apr 2004 12:31:57 -0700 (PDT)
	(envelope-from imp)
Message-Id: <200404131931.i3DJVvf4081519@repoman.freebsd.org>
From: Warner Losh <imp@FreeBSD.org>
Date: Tue, 13 Apr 2004 12:31:57 -0700 (PDT)
To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org,
	cvs-all@FreeBSD.org
X-FreeBSD-CVS-Branch: HEAD
Subject: cvs commit: src/sys/dev/pci pci.c
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Apr 2004 19:31:58 -0000

imp         2004/04/13 12:31:57 PDT

  FreeBSD src repository

  Modified files:
    sys/dev/pci          pci.c 
  Log:
  Some devices have what appear to be invalid BARs.  They are invalid in
  the sense that any write to them reads back as a 0.  This presents a
  problem to our resource allocation scheme.  If we encounter such vars,
  the code now treats them as special, allowing any allocation against
  them to succeed.  I've not seen anything in the standard to clearify
  what host software should do when it encounters these sorts of BARs.
  
  Also cleaned up some output while I'm here and add commmented out
  bootverbose lines until I'm ready to reduce the verbosity of boot
  messages.
  
  This gets a number of south bridges and ata controllers made mostly by
  VIA, AMD and nVidia working again.  Thanks to Soren Schmidt for his
  help in coming up with this patch.
  
  Revision  Changes    Path
  1.241     +51 -26    src/sys/dev/pci/pci.c