| 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 |
As for configuration sources, Debian and CentOS have been added, |
| 16 |
and the documentation has been updated to cover configuration of sources |
| 17 |
and creating new ones. |
| 18 |
|
| 19 |
Work on "hardware detection" has started. |
| 20 |
Initially, kernelconfig will scan /sys for devices with loaded modules |
| 21 |
('driver' symlink) and translate them into config options, |
| 22 |
which is rather simple to do and has no special prerequisites, |
| 23 |
but does not detect hardware for which no module has been loaded. |
| 24 |
|
| 25 |
On this basis, an "extended hardware detection" will scan devices in /sys |
| 26 |
for module aliases and translate them into module names (and then to config |
| 27 |
options). This will produce better results since 'modalias' entries exist |
| 28 |
independently from whether the module in question has been loaded, |
| 29 |
but requires creation of a 'modules.alias' file by compiling all modules once. |
| 30 |
|
| 31 |
|
| 32 |
== Plans for the next week == |
| 33 |
|
| 34 |
Get "hardware detection" mostly done. |
| 35 |
|
| 36 |
|
| 37 |
[0] https://github.com/dywisor/kernelconfig |
| 38 |
|
| 39 |
Regards, |
| 40 |
André E. |
Archives