diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-05-30 03:28:03 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-05-30 03:28:03 +0000 |
commit | cca57a53e33f77c01378141be449db3a365393dc (patch) | |
tree | 2781d07fd15486b99da574efd21c3a53ebc44006 /man | |
parent | Adding debian version 32-1. (diff) | |
download | kmod-cca57a53e33f77c01378141be449db3a365393dc.tar.xz kmod-cca57a53e33f77c01378141be449db3a365393dc.zip |
Merging upstream version 32+20240327.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'man')
-rw-r--r-- | man/modprobe.d.5.xml | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/man/modprobe.d.5.xml b/man/modprobe.d.5.xml index 2bf6537..cc90da6 100644 --- a/man/modprobe.d.5.xml +++ b/man/modprobe.d.5.xml @@ -212,6 +212,30 @@ </para> </listitem> </varlistentry> + <varlistentry> + <term>weakdep <replaceable>modulename</replaceable> <replaceable>modules...</replaceable> + </term> + <listitem> + <para> + The <command>weakdep</command> command allows you to specify weak module + dependencies. Those are similar to pre softdep, with the + difference that userspace doesn't attempt to load that + dependency before the specified module. Instead the kernel + may request one or multiple of them during module probe, + depending on the hardware it's binding to. The purpose of + weak module is to allow a driver to specify that a certain + dependency may be needed, so it should be present in the + filesystem (e.g. in initramfs) when that module is probed. + </para> + <para> + Example: Assume "weakdep c a b". A program creating an + initramfs knows it should add a, b, and c to the filesystem + since a and b may be required/desired at runtime. When c is + loaded and is being probed, it may issue calls to + request_module() causing a or b to also be loaded. + </para> + </listitem> + </varlistentry> </variablelist> </refsect1> <refsect1><title>COMPATIBILITY</title> |