From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] New Kernel Module
Date: Tue, 7 Jan 2014 23:52:09 +0800 [thread overview]
Message-ID: <20140107235209.1a53413a@skate> (raw)
In-Reply-To: <6d75f7d2.479c831d.52cc004b.8b1f5@o2.pl>
Pawel,
On Tue, 07 Jan 2014 14:25:31 +0100, makowski.pawel wrote:
> > 1. I put?an example?c file with well know hello_world example?to?/output/build/linux_xyz/samples/mykmod directory.
Don't do this. output/build is a temporary directory created only for
the duration of the build. The next time you will do "make clean", it
will be completely removed, and you will loose your changes.
Doing changes in output/build is OK is those are just for quickly
testing if a change fixes something. But any sort of development should
*NOT* be done by changing stuff in output/build.
> > 2. I create Makefile for it: obj-$(CONFIG_SAMPLE_MYKMOD) += mykmod.o
> > 3. I add the new section to KConfig in samples directory.
> ?
> When I run the make linux-menuconfig a new module is visible. So, I check it to the build.
> After issued the make command there is visible that my module is built.
> I download Kernel image and RootFs to the target and I can't find the?module file.
> Where can I find this file ? How can I menage this module ?
Check in output/target/lib/modules/<version>/ if it is there.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-01-07 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 13:25 [Buildroot] New Kernel Module makowski.pawel
2014-01-07 15:52 ` 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=20140107235209.1a53413a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox