From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Leon Gross <leon.gross@rub.de>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: List of all available kernel modules per version
Date: Thu, 23 Sep 2021 18:04:50 -0400 [thread overview]
Message-ID: <256869.1632434690@turing-police> (raw)
In-Reply-To: <3b9f6713-d66c-386d-b86b-2245b98fe0b0@rub.de>
[-- Attachment #1.1: Type: text/plain, Size: 681 bytes --]
On Thu, 23 Sep 2021 18:39:22 +0200, Leon Gross said:
> If got more of a general question: Is there a way to list all the
> standard kernel modules that are included in a specific kernel version?
> And I don't meant the currently running modules I could get via lsmod
> but I mean all the modules that are supported by a specific kernel version.
> Or can I even derive these myself from the source tree, without even
> compiling the kernel (that would be very helpful)?
One thing that you're overlooking is that many "modules" can be builtin
to the kernel rather than modprobed at runtime.
So it really depends what problem you're trying to solve by enumerating
all the modules.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-09-23 22:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 16:39 List of all available kernel modules per version Leon Gross
2021-09-23 16:57 ` Greg KH
2021-09-23 17:32 ` Leon Gross
2021-09-23 17:38 ` Greg KH
2021-09-23 17:55 ` Leon Gross
2021-09-23 18:12 ` Greg KH
2021-09-23 22:04 ` Valdis Klētnieks [this message]
2021-09-25 0:08 ` jim.cromie
2021-09-25 3:32 ` Valdis Klētnieks
2021-09-25 3:35 ` Valdis Klētnieks
2021-09-26 18:00 ` jim.cromie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=256869.1632434690@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=leon.gross@rub.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox