Date: Mon, 21 Nov 2005 18:44:28 +0100 From: "Damien Bergamini" <damien.bergamini@free.fr> To: "Nate Lawson" <nate@root.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.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: <00ff01c5eec3$3b0e6640$0300a8c0@COMETE> References: <20051119165547.0A4BD16A43D@hub.freebsd.org> <00ca01c5ed4a$86b0e570$0300a8c0@COMETE> <20051119.144210.122123926.imp@bsdimp.com> <200511211015.27879.jhb@freebsd.org> <8664qmja7y.fsf@xps.des.no> <4381F060.5040107@samsco.org> <4381FEDF.7080607@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I don't like the idea of keeping the firmware in kernel memory. It's a rather big file (~200KB). And there is one for each operating mode (BSS, IBSS, monitor). The second reason why I don't like KLDs is because they require user intervention and users must know which KLD to load for the mode they want to operate in. And if you put all firmwares in the same KLD, you end up with a big fat 1MB file. I won't go back to anything based on iwicontrol. People simply don't know how to use it. Trust me. There is not a single day where I don't get email from people complaining about it. Damien | > Or have the firmware be embedded in a KLD, like ispfw. | | I think I've now been repeated by everyone in the conversation. :) | | So maybe it's time to solve this? Move discussion to arch@? | | -- | Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00ff01c5eec3$3b0e6640$0300a8c0>