3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-26 03:31:36 +01:00
Code Issues Releases Wiki Activity

why you need to request rebuild explicitly

Browse Source
This commit is contained in:
Ciro Santilli
2018-09-13 21:10:18 +01:00
parent 3d978570bc
commit 3805a1837a
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.adoc
View File

@@ -234,6 +234,8 @@ Congratulations, you are now officially a kernel module hacker!
We use `./build-buildroot` here because kernel modules go into the root filesystem, and it is Buildroot that generates our root filesystem. The kernel modules are inside a Buildroot package.
`--kernel-modules` is required even if files were modified as explained at: <<rebuild-buildroot-packages>>.
The reboot after rebuild is annoying. We don't have a perfect solution for it yet, but there are some ideas cooking at: <<gem5-restore-new-script>>.
Not satisfied with kernel modules? OK then, let's hack up the <<linux-kernel-entry-point,entry point of the>> Linux kernel itself.
@@ -9082,6 +9084,12 @@ Since rebuilding this package is such a common case, we have a shortcut for it:
./build-buildroot --kernel-modules
....
The rebuild must be requested explicitly, otherwise the package does not rebuild, even if its files were modified.
This is because Buildroot builds dozens of packages, and just reading there Makefiles and checking the stamps generates too much overhead
So you must tell Buildroot yourself about the rebuild.
=== Custom Buildroot configs
We provide the following mechanisms: