Date: Tue, 13 Jun 2000 12:42:46 -0600 From: Warner Losh <imp@village.org> To: Terry Lambert <tlambert@primenet.com> Cc: arch@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pci.c pcisupport.c pcivar.h Message-ID: <200006131842.MAA16232@harmony.village.org> In-Reply-To: Your message of "Tue, 13 Jun 2000 16:37:49 -0000." <200006131637.JAA08514@usr05.primenet.com> References: <200006131637.JAA08514@usr05.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200006131637.JAA08514@usr05.primenet.com> Terry Lambert writes: : > In message <8947.960886026@critter.freebsd.dk> Poul-Henning Kamp writes: : > : "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? : : 1) Register them in a file : : 2) Read the file using kernel level file I/O : : 3) For simplicity sake, make each line in the file a fixed : length; though some additional variable length text : record stuff in the kernel would be useful eventually, : the "edquota" approach is reasonable. I thought we were trying to get away from having all this information in a centralized repository... The drivers already know this and adding an additional file for this info seems to be asking for problems. I know on Solaris it was from time to time... Warner 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?200006131842.MAA16232>