From: Greg KH <greg@kroah.com>
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:57:28 +0200 [thread overview]
Message-ID: <YUyx+KrWiQYiROI4@kroah.com> (raw)
In-Reply-To: <3b9f6713-d66c-386d-b86b-2245b98fe0b0@rub.de>
On Thu, Sep 23, 2021 at 06:39:22PM +0200, Leon Gross wrote:
> Hi everyone,
>
> 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?
What do you mean by "standard" exactly?
What architecture? What types of hardware do you feel are "standard"?
> 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)?
A random list of module names probably does not help much (hint, what
hardware does the module that is called "option.ko" support?")
What problem are you trying to solve here?
thanks,
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-09-23 16:57 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 [this message]
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
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=YUyx+KrWiQYiROI4@kroah.com \
--to=greg@kroah.com \
--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