From owner-freebsd-arch  Tue Jun 13  9:26:38 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 BDC8737BF0B; Tue, 13 Jun 2000 09:26:34 -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 JAA03448;
	Tue, 13 Jun 2000 09:25:45 -0700
Date: Tue, 13 Jun 2000 09:25:40 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Warner Losh <imp@village.org>
Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>,
	Doug Rabson <dfr@nlsystems.com>, Doug Rabson <dfr@FreeBSD.ORG>,
	arch@FreeBSD.ORG
Subject: Re: cvs commit: src/sys/pci pci.c pcisupport.c pcivar.h 
In-Reply-To: <200006131620.KAA14918@harmony.village.org>
Message-ID: <Pine.BSF.4.05.10006130923440.2214-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> : "Found <FOOcorp magicchip 1242> Configure \"blaha\" driver in your kernel"
> : 
> : I can see all the bloat arguments, but I have to say that the idea
> : has some merit...
> 
> How could the kernel know all possible device drivers, even third
> party ones?

That's the point about how Solaris does this (or did- originally).

I have a card identifying itself as "Fred". At boot (or boot/reconfigure)
time, you tentatively load all drivers and enter their identify entry point
with a dev_info_t asking, "do you drive this device?". Simple enough. The hard
part is to try (if you think it's important) to arbitrate between several
different drivers who want to drive that device.

-matt




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