From owner-freebsd-arch  Mon Jun 12 23:23: 7 2000
Delivered-To: freebsd-arch@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8CDAB37B77A; Mon, 12 Jun 2000 23:23:04 -0700 (PDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA04942;
	Tue, 13 Jun 2000 00:23:01 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA12159; Tue, 13 Jun 2000 00:21:57 -0600 (MDT)
Message-Id: <200006130621.AAA12159@harmony.village.org>
To: Doug Rabson <dfr@FreeBSD.org>
Subject: Re: cvs commit: src/sys/pci pci.c pcisupport.c pcivar.h 
Cc: arch@FreeBSD.org
In-reply-to: Your message of "Fri, 09 Jun 2000 09:00:31 PDT."
		<200006091600.JAA25038@freefall.freebsd.org> 
References: <200006091600.JAA25038@freefall.freebsd.org>  
Date: Tue, 13 Jun 2000 00:21:57 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <200006091600.JAA25038@freefall.freebsd.org> Doug Rabson writes:
: dfr         2000/06/09 09:00:31 PDT
: 
:   Modified files:
:     sys/pci              pci.c pcisupport.c pcivar.h 
:   Log:
:   Nuke the useless chip driver. It gets in the way when you want to load
:   a functional driver for the device.
:   
:   Revision  Changes    Path
:   1.153     +2 -1      src/sys/pci/pci.c
:   1.163     +3 -51     src/sys/pci/pcisupport.c
:   1.46      +2 -1      src/sys/pci/pcivar.h

Personally I think that we should add it back as a "loose" or
"generic" device after I finish the work on the unknown driver.  This
would allow you to do the same thing, and still have decent boot
messages.

Warner


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message