Date: Mon, 21 Nov 2005 13:44:37 -0500 (EST) From: Daniel Eischen <deischen@freebsd.org> To: Warner Losh <imp@bsdimp.com> 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: <Pine.GSO.4.43.0511211338260.24616-100000@sea.ntplx.net> In-Reply-To: <20051121.113052.71133065.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 21 Nov 2005, Warner Losh wrote: > > 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. Not taking one side or the other... Can we use a common tool to convert firmware to a kld? Just pass it the symbol name or whatever else you need? I guess this makes the assumption that most firmware consists of just one object file. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.43.0511211338260.24616-100000>