Date: Mon, 21 Nov 2005 11:30:52 -0700 (MST) From: Warner Losh <imp@bsdimp.com> To: scottl@samsco.org Cc: arch@freebsd.org, nate@root.org Subject: Re: cvs commit: src/sys/modules/iwi Makefile src/sys/dev/iwi if_iwi.c if_iwireg.h if_iwivar.h Message-ID: <20051121.113052.71133065.imp@bsdimp.com> In-Reply-To: <43821134.6040306@samsco.org> References: <4381FEDF.7080607@root.org> <20051121.111955.74713410.imp@bsdimp.com> <43821134.6040306@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Making the driver aware of the filesystem layout is a bad idea. Your opinion has been noted. Repeating it often isn't going to help. It has its advantages from the user point of view (I put a file here and it is used, my tool of choice can always be "cp"). > Encapsulating data into a KLD is not hard to do. Neither is a dozen other things that we do automatically for the user. From a user point of view this is a pita. I put this file here, and then I have to remember which magic tool to run to convert the iwi firmware into a kld. But that's a different tool from the wi driver and that's different from the iwp driver, etc. Each approach has its pro's and con's. Getting dogmatic about 'X is a bad idea, therefor you must do Y' without looking at why 'Y' might be a worse alternative to 'X' isn't going to help this discussion. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051121.113052.71133065.imp>