| 1 |
Hi everyone, |
| 2 |
|
| 3 |
|
| 4 |
== Brief summary of this project == |
| 5 |
|
| 6 |
kernelconfig is about generating kernel configuration files, |
| 7 |
using various sources such as curated defconfigs, detected hardware, |
| 8 |
installed packages and user input. |
| 9 |
|
| 10 |
The project's code can be found at [0]. |
| 11 |
|
| 12 |
|
| 13 |
== This week's progress == |
| 14 |
|
| 15 |
This week's work has been about extending hardware detection. |
| 16 |
|
| 17 |
Creation of files necessary for "modalias"-based hardware detection has |
| 18 |
been added. Basically, "make allmodconfig && make modules" is run to create |
| 19 |
all modules, and the desired "modules.alias" file is then created with depmod. |
| 20 |
Since this takes a lot of time to compile, it is not done automatically. |
| 21 |
Instead, kernelconfig offers a command for creating "modalias" files, |
| 22 |
and tries to use previously created files (depending on e.g. kernel version). |
| 23 |
|
| 24 |
A "hardware collector" shell script has been written, |
| 25 |
which allows to detect required/useful kernel modules on another machine |
| 26 |
than the one configuring/building the kernel. |
| 27 |
The idea here is to run this script on a live system (practically |
| 28 |
anything with a few busybox applets), and feed kernelconfig with the data. |
| 29 |
|
| 30 |
|
| 31 |
== Plans for the next week == |
| 32 |
|
| 33 |
* write documentation for "hardware detection" |
| 34 |
|
| 35 |
* start with "pm integration", |
| 36 |
so far there is a draft-doc [1] on what could be done |
| 37 |
|
| 38 |
|
| 39 |
[0] https://github.com/dywisor/kernelconfig |
| 40 |
[1] https://github.com/dywisor/kernelconfig/blob/2f4ceefc79d2ca677e63537ade42d6bff10d0e00/doc/rst/draft/pmintegration.rst |
| 41 |
|
| 42 |
Regards, |
| 43 |
André E. |
Archives