1 |
On 2022.04.06 14:51, Jude DaShiell wrote: |
2 |
> I'm curious, with a system about to build a kernel does a command or |
3 |
> command switch exist to tell the kernel build process to build the |
4 |
> kernel |
5 |
> in such a way that all hardware now enabled gets enabled in the build |
6 |
> of |
7 |
> the kernel? |
8 |
Which pieces get built into the kernel (or as loadable modules) is |
9 |
controlled by .config. To get the new kernel to include all the |
10 |
drivers/modules enabled in the current kernel, you can "zcat |
11 |
/proc/config.gz > .config" in the new /usr/src/linux. (That does |
12 |
assume the running kernel is built with the parameters to create |
13 |
/proc/config.gz.) Then run "make oldconfig" (or one of it's variants) |
14 |
to include new lines to .config. To see (a subset) of those modules |
15 |
are actually used by existing hardware, do "lspci -k". I don't know of |
16 |
any script to automatically parse that output, although I wouldn't be |
17 |
surprised if there was one (or more.) Note hat probably won't include |
18 |
modules used for usb devices, just the usb hubs. Currently loaded |
19 |
modules can be listed with lsmod, but that doesn't include anything |
20 |
built in. |
21 |
|
22 |
Is a11y a typo, or just something I don't understand? If you mean to |
23 |
say (all Y) Y to all kernel config questions, I believe there is a make |
24 |
option for the kernel which will do that - but I'd have to read the |
25 |
docs for the details. Also, while that's of use for a distro kernel |
26 |
(where you have no idea what will be in PCs where it gets used) it will |
27 |
add lots of stuff to the kernel that you are unlikely to ever use. |
28 |
What is your actual goal? |
29 |
|
30 |
Jack |