From owner-freebsd-current@FreeBSD.ORG Mon May 5 05:45:44 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9FB237B404 for ; Mon, 5 May 2003 05:45:42 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 137F643F93 for ; Mon, 5 May 2003 05:45:42 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h45CjfA7043019; Mon, 5 May 2003 06:45:41 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 05 May 2003 06:44:22 -0600 (MDT) Message-Id: <20030505.064422.32059949.imp@bsdimp.com> To: ebakke@trolltech.com From: "M. Warner Losh" In-Reply-To: <200305051435.12481.ebakke@trolltech.com> References: <200305051222.05046.doconnor@gsoft.com.au> <20030505.062203.30240784.imp@bsdimp.com> <200305051435.12481.ebakke@trolltech.com> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Floppy Support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 May 2003 12:45:45 -0000 In message: <200305051435.12481.ebakke@trolltech.com> "Erik H. Bakke" writes: : -----BEGIN PGP SIGNED MESSAGE----- : Hash: SHA1 : : On Monday 05 May 2003 14:22, M. Warner Losh wrote: : > : Or use modules.. : > : The vast majority of drivers are loadable as modules. It would be : > : feasible to standardise the PCI ID tables of drivers and then generate a : > : list from it which you can use to load modules for cards you find. : > : > There's more than just pci ID. Also, there are a couple of drivers : > that don't base their decision on the pci id, but other things in the : > headers to attach to all devices of a certain class. This makes : > autoloading a little harder. : > : Wouldn't this be the drivers that would always be on the kernel floppy? Not necessarily. Cardbus bridges fall into this category as do many of the usb drivers and some of the bluetooth stuff. This is in addition to the sio, ppc, and those sorts of generic drivers. : I think the drivers that would be candidates for autoloading based on PCI ID : would be more specialized drivers, and typically not drivers for things such : as IDE controllers, bus bridges, etc. These are good candidates. You really only need your '/' device compiled into the kernel. All else can be autoloaded. There's an issue with cam scsi drivers at the moment that requires a userland workaround (camcontrol rescan) when you load one of these drivers. You really want something like devd to do the loading, but that might be merged into sysinstall. Standardizing the drivers so that one can generate the tables isn't too hard, but is tedious and leads into many-a-bikeshed for unsuspecting victums. Warner