Date: Wed, 24 Jul 2002 22:39:31 -0600 From: Scott Long <scott_long@btc.adaptec.com> To: "M. Warner Losh" <imp@bsdimp.com> Cc: matusita@jp.FreeBSD.org, ru@freebsd.org, current@freebsd.org Subject: Re: cvs commit: src/release/i386 drivers.conf Message-ID: <20020725043931.GB50119@hollin.btc.adaptec.com> In-Reply-To: <20020724.184701.17239163.imp@bsdimp.com> References: <20020705005426Y.matusita@jp.FreeBSD.org> <20020724173037.GE87477@sunbay.com> <20020725032910A.matusita@jp.FreeBSD.org> <20020724.184701.17239163.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 24, 2002 at 06:47:01PM -0600, M. Warner Losh wrote: > In message: <20020725032910A.matusita@jp.FreeBSD.org> > Makoto Matsushita <matusita@jp.FreeBSD.org> writes: > : > : ru> This was "broken" again. I don't have any ideas of what to move > : ru> out. > : > : There are some ideas to do around boot floppies in my mind: > : > : 1) More drivers to move kernel modules, including other network > : drivers, pccard and friends, filesystems, etc. Apparantly it > : reduces kernel size so kern.flp will fit to 1.44MB again. It > : requires some consideration that which driver can be moved as a > : kernel module. > > I've noticed that some of the older cam drivers are about all that is > in the way of making CAM truly loadable. By that I mean having a > kernel with all supported devices that aren't loadable forces CAM to > be in the kernel because some of the SCSI devices aren't (yet) > loadable. However, that's relatively easy to fix. > > Warner Makeing ahc and ahd loadable is in our pipeline. It's somewhat hindered by the dependancy on the firmware compiler, so it's not as trivial as it seems. People are welcome to tackle the other CAM drivers. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020725043931.GB50119>