From: Andreas Ziegler <br015@umbiko.net>
To: "Esaïe Ledoux NJONGSSI KOUAM" <kouamdoux@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] how can i implement my kernel module and debug it
Date: Tue, 19 Oct 2021 05:47:34 +0000 [thread overview]
Message-ID: <3f8142a1afd59acc55e141f2d8a95e66@umbiko.net> (raw)
In-Reply-To: <CA+eej5PtS6iCJ+W1b6W0mZXk-fQJcB1hhr20_D7cE=fja8NzTw@mail.gmail.com>
Hi Esaïe
<appended Buildroot list>
On 2021-10-18 23:19, Esaïe Ledoux NJONGSSI KOUAM wrote:
> my kernel module works very well ,
>
> in qemu , i have type lsmod , but nothing , doesn't it means that
> linux kernel image doesn't build ??
<cut>
With the original config files, the module will not be built. Once it
gets built, the missing modules_install may prevent copying it into
/lib/modules in the target.
To see which steps were executed by Buildroot, run
$ grep kernel-module build/build-time.log
This file contains timestamps of all tasks executed by the Buildroot
environment.
> i have make something like you have said , but the problem still occur
-- Make sure your configuration is visible to Buildroot. You must be
able to select it in the menu editor (make nconfig).
-- Build your module separately by calling 'make kernel-module-rebuild'
and analyze the output. You should get headings for the separate build
steps (downloading, extracting, patching, configuring, building,
installing). Some sections may be missing or empty, but at least
'building/installing' must show output from your module. You might also
run build steps separately, until you find the one that fails; see [4]
-- Verify that the directory build/kernel-module exists and contains the
expected files.
-- Check target/lib/modules/${BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE} to
see if your module is included.
Kind regards,
Andreas
[4] https://buildroot.org/downloads/manual/manual.html#pkg-build-steps
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-19 5:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.16364.1634462006.241441.buildroot@buildroot.org>
2021-10-17 9:45 ` [Buildroot] how can i implement my kernel module and debug it Andreas Ziegler
[not found] ` <CA+eej5PtS6iCJ+W1b6W0mZXk-fQJcB1hhr20_D7cE=fja8NzTw@mail.gmail.com>
2021-10-19 5:47 ` Andreas Ziegler [this message]
2021-10-19 14:34 ` Esaïe Ledoux NJONGSSI KOUAM
2021-10-19 12:45 ` Arnout Vandecappelle
2021-10-20 7:17 ` Andreas Ziegler
2021-10-21 7:58 ` Esaïe Ledoux NJONGSSI KOUAM
2021-10-21 6:41 ` Andreas Ziegler
2021-10-21 10:51 ` Esaïe Ledoux NJONGSSI KOUAM
2021-10-16 16:57 Esaïe Ledoux NJONGSSI KOUAM
2021-10-16 17:21 ` Esaïe Ledoux NJONGSSI KOUAM
2021-10-17 15:45 ` Arnout Vandecappelle
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=3f8142a1afd59acc55e141f2d8a95e66@umbiko.net \
--to=br015@umbiko.net \
--cc=buildroot@buildroot.org \
--cc=kouamdoux@gmail.com \
/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.