Date: Sun, 20 Nov 2005 09:53:22 -0800 From: Sam Leffler <sam@errno.com> To: Mike Silbersack <silby@silby.com> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, Damien Bergamini <damien@FreeBSD.org>, cvs-all@FreeBSD.org, Nate Lawson <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: <4380B812.7020507@errno.com> In-Reply-To: <20051120013533.F10822@odysseus.silby.com> References: <200511191654.jAJGsu9n022860@repoman.freebsd.org> <43801038.7050109@errno.com> <438023A1.50002@root.org> <20051120013533.F10822@odysseus.silby.com>
index | next in thread | previous in thread | raw e-mail
Mike Silbersack wrote: > > On Sat, 19 Nov 2005, Nate Lawson wrote: > >> Right, but such an approach won't work for storage drivers like >> isp(4). Couldn't you just generalize the approach used by ispfw(4)? >> It uses the kld module approach to get the firmware into kernel memory. >> >> -- >> Nate > > > For something like a network driver, preloading the firmware into a kld > is a waste of memory. The exception would be if you were to try > netbooting from a iwi card, but that seems unlikely to be a common problem. > > Until someone does come up with the official "FreeBSD" way to load > firmware, let's stop kibitzing about this commit and let Damien get back > to work. It's not a question of kibbitzing; there's been discussion about dealing with this issue with a general mechanism and not sticking individual solutions in drivers. Doing this would mean not having to answer the immediate followup questions like "what about ipw". Samhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4380B812.7020507>