From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Nicolas_de_Peslo=FCan?= Date: Tue, 30 Aug 2011 08:46:51 +0200 Subject: BCM4321 support In-Reply-To: References: <4E5AB689.4010000@lwfinger.net> <4E5BC004.8060608@lwfinger.net> Message-ID: <4E5C875B.9030602@free.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: b43-dev@lists.infradead.org Le 30/08/2011 01:33, Octavian Voicu a ?crit : > On Tue, Aug 30, 2011 at 12:42 AM, Nicolas de Peslo?an > wrote: > > The clean way is make deb-pkg from the root of the kernel tree. It will build whatever need to > be build (normal build), then build several .deb files you can install using dpkg -i. The normal > build takes "normal build time", but building the .deb files takes several minutes. I don't > consider this a problem, but... > > The fastest way is to simply make, then copy the changed modules into /lib/modules/..., but from > a debian point of view, it is very dirty. > > > Yeah, I guess I prefer the very quick and dirty way. I added them to /lib/modules/.../updates/ and > ran depmod. Good enough for me. As long as I don't dig too deep in b43 I probably won't need to do > full kernel builds. > > My biggest concern right now is that the modules I build cannot be rmmod-ed after being inserted. > This happens with any custom built modules, including the dkms built ones (eg. nvidia). I really suggest you once try building the whole kernel with deb-pkg, then touch a single file in b43, then rebuild. The overhead of producing .deb files is not null, but not big enough to stop me from rebuilding on every try. And I assume it would solve this module unload issue. Nicolas.