From: "Nicolas de Pesloüan" <nicolas.2p.debian@free.fr>
To: b43-dev@lists.infradead.org
Subject: BCM4321 support
Date: Tue, 30 Aug 2011 08:46:51 +0200 [thread overview]
Message-ID: <4E5C875B.9030602@free.fr> (raw)
In-Reply-To: <CAM0=5GsX2W7oLXY+WuP+sYJFqWqAOCcKqaqY6UCxFnNBvR3iiw@mail.gmail.com>
Le 30/08/2011 01:33, Octavian Voicu a ?crit :
<snip>
> On Tue, Aug 30, 2011 at 12:42 AM, Nicolas de Peslo?an <nicolas.2p.debian@free.fr
> <mailto:nicolas.2p.debian@free.fr>> 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.
next prev parent reply other threads:[~2011-08-30 6:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 16:33 BCM4321 support Octavian Voicu
2011-08-24 16:42 ` Octavian Voicu
2011-08-24 16:55 ` Rafał Miłecki
2011-08-24 18:32 ` Octavian Voicu
2011-08-24 21:11 ` Rafał Miłecki
2011-08-27 14:57 ` Octavian Voicu
2011-08-27 18:13 ` Gábor Stefanik
2011-08-28 16:59 ` Octavian Voicu
2011-08-28 21:43 ` Larry Finger
2011-08-29 13:08 ` Octavian Voicu
2011-08-29 16:36 ` Larry Finger
2011-08-29 21:42 ` Nicolas de Pesloüan
2011-08-29 23:33 ` Octavian Voicu
2011-08-30 6:46 ` Nicolas de Pesloüan [this message]
2011-08-29 23:46 ` Michael Büsch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E5C875B.9030602@free.fr \
--to=nicolas.2p.debian@free.fr \
--cc=b43-dev@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.