I'm curious, with a system about to build a kernel does a command or
command switch exist to tell the kernel build process to build the kernel
in such a way that all hardware now enabled gets enabled in the build of
the kernel?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2022.04.06 14:51, Jude DaShiell wrote:

I'm curious, with a system about to build a kernel does a command or
command switch exist to tell the kernel build process to build the
kernel
in such a way that all hardware now enabled gets enabled in the build
of
the kernel?

Which pieces get built into the kernel (or as loadable modules) is
controlled by .config. To get the new kernel to include all the drivers/modules enabled in the current kernel, you can "zcat
/proc/config.gz > .config" in the new /usr/src/linux. (That does
assume the running kernel is built with the parameters to create /proc/config.gz.) Then run "make oldconfig" (or one of it's variants)
to include new lines to .config. To see (a subset) of those modules
are actually used by existing hardware, do "lspci -k". I don't know of
any script to automatically parse that output, although I wouldn't be surprised if there was one (or more.) Note hat probably won't include modules used for usb devices, just the usb hubs. Currently loaded
modules can be listed with lsmod, but that doesn't include anything
built in.

Is a11y a typo, or just something I don't understand? If you mean to
say (all Y) Y to all kernel config questions, I believe there is a make option for the kernel which will do that - but I'd have to read the
docs for the details. Also, while that's of use for a distro kernel
(where you have no idea what will be in PCs where it gets used) it will
add lots of stuff to the kernel that you are unlikely to ever use.
What is your actual goal?

Jack

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

#a11y is an accessibility hash tag you may run across on the internet.
That covers assistive technologies like screen readers; refreshable
braille displays, magnifiers, and similar other technologies I've been fortunate to have never needed to use for work on technology.
The information you provided I think will help my next gentoo install go
better in the kernel build phase thanks.


On Wed, 6 Apr 2022, Jack wrote:

On 2022.04.06 14:51, Jude DaShiell wrote:

I'm curious, with a system about to build a kernel does a command or >command switch exist to tell the kernel build process to build the kernel >in such a way that all hardware now enabled gets enabled in the build of >the kernel?

Which pieces get built into the kernel (or as loadable modules) is controlled by .config. To get the new kernel to include all the drivers/modules enabled in the current kernel, you can "zcat /proc/config.gz > .config" in the new /usr/src/linux. (That does assume the running kernel is built with the parameters to create /proc/config.gz.) Then run "make oldconfig" (or one of it's variants) to include new lines to .config. To see (a subset) of those modules are actually used by existing hardware, do "lspci -k". I don't know of any script to automatically parse that output, although I wouldn't be surprised if there was one (or more.) Note hat probably won't include modules
used for usb devices, just the usb hubs. Currently loaded modules can be listed with lsmod, but that doesn't include anything built in.

Is a11y a typo, or just something I don't understand? If you mean to say (all
Y) Y to all kernel config questions, I believe there is a make option for the kernel which will do that - but I'd have to read the docs for the details. Also, while that's of use for a distro kernel (where you have no idea what will be in PCs where it gets used) it will add lots of stuff to the kernel that you are unlikely to ever use. What is your actual goal?

Jack

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Am Mittwoch, 6. April 2022, 20:51:05 CEST schrieb Jude DaShiell:

I'm curious, with a system about to build a kernel does a command or
command switch exist to tell the kernel build process to build the kernel
in such a way that all hardware now enabled gets enabled in the build of
the kernel?

It seems to me you are searching for "make localmodconfig" (but I could be wrong).

See more here: https://www.kernel.org/doc/html/latest/admin-guide/README.html#configuring-the-kernel

Many Greetings,
Peter

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Ah - a11y sort of like i18n and l10n (at least in how to read it.) I
just found a web page calling it a numeronym.

After all your reading, I would still suggest thinking carefully about
your goal. The link Peter sent has a good summary of all the "make Xc
onfig" options, and I agree with him that "make localmodconfig" sounds
like what you want. Extra "Y" or "M" in your config might save you
from recompiling the kernel again later, but it makes your kernel
larger, and take longer to compile and load, although how much those
delays bother you is very personal.

Jack

On 2022.04.06 17:16, Jude DaShiell wrote:

#a11y is an accessibility hash tag you may run across on the internet.
That covers assistive technologies like screen readers; refreshable
braille displays, magnifiers, and similar other technologies I've been fortunate to have never needed to use for work on technology.
The information you provided I think will help my next gentoo install
go
better in the kernel build phase thanks.

On Wed, 6 Apr 2022, Jack wrote:

On 2022.04.06 14:51, Jude DaShiell wrote:

I'm curious, with a system about to build a kernel does a command

or

command switch exist to tell the kernel build process to build the

kernel

in such a way that all hardware now enabled gets enabled in the

build of

the kernel?

Which pieces get built into the kernel (or as loadable modules) is

controlled

by .config. To get the new kernel to include all the

drivers/modules enabled

in the current kernel, you can "zcat /proc/config.gz > .config" in

the new

/usr/src/linux. (That does assume the running kernel is built with

the

parameters to create /proc/config.gz.) Then run "make oldconfig"

(or one of

it's variants) to include new lines to .config. To see (a subset)

of those

modules are actually used by existing hardware, do "lspci -k". I

don't know

of any script to automatically parse that output, although I

wouldn't be

surprised if there was one (or more.) Note hat probably won't

include modules

used for usb devices, just the usb hubs. Currently loaded modules

can be

listed with lsmod, but that doesn't include anything built in.

Is a11y a typo, or just something I don't understand? If you mean

to say (all

Y) Y to all kernel config questions, I believe there is a make

option for the

kernel which will do that - but I'd have to read the docs for the

details.

Also, while that's of use for a distro kernel (where you have no

idea what

will be in PCs where it gets used) it will add lots of stuff to the

kernel

that you are unlikely to ever use. What is your actual goal?

Jack

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)