From owner-freebsd-arch Tue Jun 13 10:12:19 2000 Delivered-To: freebsd-arch@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D175137BFB8; Tue, 13 Jun 2000 10:12:15 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA03809; Tue, 13 Jun 2000 10:12:14 -0700 Date: Tue, 13 Jun 2000 10:12:09 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: arch@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pci.c pcisupport.c pcivar.h In-Reply-To: <200006131713.KAA22419@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Our plans already cover this (more or less) - we put metadata in the > driver object so you don't actually have to load it to decide whether > it's a contender, and we have an arbitration scheme in place already. I'm not sure that metadata is the right thing to do since you can't always statically assign dependencies. But, to be fair, dynamic dependency mechanisms in recent systems haven't been w/o their problems as well. > > The issue is - why print a message when you can just load the damn driver > already? > To take the other side of the argument 'as a transitional feature'? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message