From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building / installing kernel modules.
Date: Thu, 10 Oct 2013 09:02:58 +0200 [thread overview]
Message-ID: <20131010090258.23617c17@skate> (raw)
In-Reply-To: <8DEC37E638F84029919B5EB7D735370D@JohanW7>
Dear Sagaert Johan,
On Wed, 9 Oct 2013 20:37:35 +0200, Sagaert Johan wrote:
> I found this post http://lists.busybox.net/pipermail/buildroot/2011-July/044690.html
Note that this post was made by Thomas De Schampheleire, not me. Yeah,
I know, two Thomas, it's confusing :)
> Has there been some infrastructure added to aid in building and installing kernel modules ?
No. In fact I'm not sure there is really a need for that.
> I created a generic-package makefile to build and install the kernel module.
> So far so good, but I still have to run depmod -a on my target to register the module.
>
> How can I use the post_install hook to have the module registered by buildroot,
> so I don't have to do it on my target board ?
Normally, if you use the modules_install target of the kernel Makefile
to install your own modules, it should call depmod automatically.
See
http://lists.busybox.net/pipermail/buildroot/2011-August/044807.html
for an example that does this (if I remember correctly).
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-10-10 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 18:37 [Buildroot] Building / installing kernel modules Sagaert Johan
2013-10-10 7:02 ` Thomas Petazzoni [this message]
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=20131010090258.23617c17@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.