Date: Tue, 13 Jun 2000 10:13:49 -0700 From: Mike Smith <msmith@freebsd.org> To: mjacob@feral.com Cc: arch@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pci.c pcisupport.c pcivar.h Message-ID: <200006131713.KAA22419@mass.cdrom.com> In-Reply-To: Your message of "Tue, 13 Jun 2000 09:25:40 PDT." <Pine.BSF.4.05.10006130923440.2214-100000@semuta.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > : "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. 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. The issue is - why print a message when you can just load the damn driver already? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006131713.KAA22419>