[ sparring ] Are the linux drivers in the kernel !?

[xor]

[ sparring ] Are the linux drivers in the kernel !?

if they are never used, it will cause unnecessary space and resource consumption.

if this is so! Does TCL need to revise its kernel philosophy!?

[Juanito]

See http://www.tinycorelinux.net/12.x/x86_64/release/src/kernel/config-5.10.3-tinycore64

"=y" compiled into the kernel
"=m" compiled as a module

[xor]

options here
add driver to kernel
or
create a separate plugin file
in shape!?

So what should I do to not compile a non-existent hardware driver other than these 2 options!?

[Juanito]

There are actually three options:

"=y"
"=m"
"is not set"

..nothing will be done if "is not set" is chosen.

Note also that the majority of the drivers compiled with "=m" are available in the extensions named *-5.10.3-tinycore64. There are a few drivers in the base contained in modules64.gz (corepure64.gz = rootfs64.gz + modules64.gz).

[xor]

okay, I got it ; There is an option that remains hidden!

2nd question ; According to the previous comment section;

does this affect ram space consumption!?

will logically affect

there seems to be a 512 mb kernel dependency consumption in the middle!

If you really want to make TCL smaller, which way should you follow!?

FWUPD Linux Firmware Updater Prepares "Best Known Configuration" Feature
https://www.phoronix.com/forums/forum/hardware/general-hardware/1293412-fwupd-linux-firmware-updater-prepares-best-known-configuration-featurers

[Juanito]

Kernel drivers compiled as modules and included in extensions will have a minimal effect on ram if and when a module is loaded.

Kernel drivers compiled into the kernel or compiled as modules and included in the base will have a bigger effect on ram as the init.rd modules64.gz and vmlinuz64 are loaded into ram at boot.

I’m not sure why you included the link to firmware?