Home
last modified time | relevance | path

Searched full:modules (Results 1 – 25 of 2763) sorted by relevance

12345678910>>...111

/kernel/linux/linux-4.19/samples/
DKconfig10 tristate "Build trace_events examples -- loadable modules only"
13 This build trace event example modules.
23 tristate "Build kobject examples -- loadable modules only"
27 different kobject sample modules showing how to use kobjects,
33 tristate "Build kprobes examples -- loadable modules only"
36 This build several kprobes example modules.
39 tristate "Build kretprobes example -- loadable modules only"
47 This builds kernel hardware breakpoint example modules.
50 tristate "Build kfifo examples -- loadable modules only"
54 different kfifo sample modules showing how to use the
[all …]
/kernel/linux/linux-4.19/Documentation/kbuild/
Dmodules.txt1 Building External Modules
8 === 2 How to Build External Modules
17 --- 3.4 Building Multiple Modules
26 --- 6.1 Symbols From the Kernel (vmlinux + modules)
27 --- 6.2 Symbols and External Modules
36 "kbuild" is the build system used by the Linux kernel. Modules must use
38 to pick up the right flags to "gcc." Functionality for building modules
40 either is similar, and all modules are initially developed and built
44 in building out-of-tree (or "external") modules. The author of an
51 === 2. How to Build External Modules
[all …]
/kernel/linux/linux-4.19/Documentation/admin-guide/
Dmodule-signing.rst10 .. - Manually signing modules.
11 .. - Signed modules and stripping.
12 .. - Loading signed modules.
13 .. - Non-valid signatures and unsigned modules.
21 The kernel module signing facility cryptographically signs modules during
23 allows increased kernel security by disallowing the loading of unsigned modules
24 or modules signed with an invalid key. Module signing increases security by
49 (1) :menuselection:`Require modules to be validly signed`
55 If this is off (ie. "permissive"), then modules for which the key is not
56 available and modules that are unsigned are permitted, but the kernel will
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dmodule-signing.rst10 .. - Manually signing modules.
11 .. - Signed modules and stripping.
12 .. - Loading signed modules.
13 .. - Non-valid signatures and unsigned modules.
21 The kernel module signing facility cryptographically signs modules during
23 allows increased kernel security by disallowing the loading of unsigned modules
24 or modules signed with an invalid key. Module signing increases security by
49 (1) :menuselection:`Require modules to be validly signed`
55 If this is off (ie. "permissive"), then modules for which the key is not
56 available and modules that are unsigned are permitted, but the kernel will
[all …]
/kernel/linux/linux-5.10/Documentation/kbuild/
Dmodules.rst2 Building External Modules
10 === 2 How to Build External Modules
19 --- 3.4 Building Multiple Modules
28 --- 6.1 Symbols From the Kernel (vmlinux + modules)
29 --- 6.2 Symbols and External Modules
39 "kbuild" is the build system used by the Linux kernel. Modules must use
41 to pick up the right flags to "gcc." Functionality for building modules
43 either is similar, and all modules are initially developed and built
47 in building out-of-tree (or "external") modules. The author of an
54 2. How to Build External Modules
[all …]
Dkbuild.rst9 modules.order
11 This file records the order in which modules appear in Makefiles. This
13 multiple modules.
15 modules.builtin
17 This file lists all modules that are built into the kernel. This is used
20 modules.builtin.modinfo
22 This file contains modinfo from all modules that are built into the kernel.
37 Additional options to the assembler (for built-in and modules).
41 Additional assembler options for modules.
49 Additional options to the C compiler (for built-in and modules).
[all …]
/kernel/linux/linux-5.10/samples/
DKconfig14 tristate "Build trace_events examples -- loadable modules only"
17 This build trace event example modules.
45 different kobject sample modules showing how to use kobjects,
51 tristate "Build kprobes examples -- loadable modules only"
54 This build several kprobes example modules.
57 tristate "Build kretprobes example -- loadable modules only"
65 This builds kernel hardware breakpoint example modules.
68 tristate "Build kfifo examples -- loadable modules only"
72 different kfifo sample modules showing how to use the
78 tristate "Build kdb command example -- loadable modules only"
[all …]
/kernel/linux/linux-5.10/drivers/gpu/drm/amd/display/
DMakefile32 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/inc
33 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/freesync
34 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/color
35 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/info_packet
36 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/power
40 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/hdcp
46 DAL_LIBS = amdgpu_dm dc modules/freesync modules/color modules/info_packet modules/power dmub/src
49 DAL_LIBS += modules/hdcp
/kernel/linux/linux-5.10/scripts/
DMakefile.modpost11 # d) modules.order, which lists all the modules
14 # 1) Find all modules listed in modules.order
32 # Step 4 is solely used to allow module versioning in external modules,
37 # KBUILD_MODPOST_NOFINAL can be set to skip the final link of modules.
68 output-symdump := modules-only.symvers
76 Module.symvers: vmlinux.symvers modules-only.symvers FORCE
85 # set src + obj - they may be used in the modules's Makefile
93 # modpost option for external modules
101 # modpost options for modules (both in-kernel and external)
107 # 'make -i -k' ignores compile errors, and builds as many modules as possible.
[all …]
DMakefile.modinst3 # Installing modules
11 modules := $(sort $(shell cat $(if $(KBUILD_EXTMOD),$(KBUILD_EXTMOD)/)modules.order))
13 PHONY += $(modules)
14 __modinst: $(modules)
17 # Don't stop modules_install if we can't sign external modules.
26 # Modules built outside the kernel source tree go into extra by default
32 $(modules):
DMakefile.modsign3 # Signing modules
11 modules := $(sort $(shell cat modules.order))
13 PHONY += $(modules)
14 __modsign: $(modules)
20 # Modules built outside the kernel source tree go into extra by default
26 $(modules):
Ddepmod.sh30 mkdir -p "$tmp_dir/lib/modules/$KERNELRELEASE"
32 if test -e "$tmp_dir/lib/modules/$KERNELRELEASE/modules.dep" -o \
33 -e "$tmp_dir/lib/modules/$KERNELRELEASE/modules.dep.bin"; then
39 symlink="$INSTALL_MOD_PATH/lib/modules/99.98.$KERNELRELEASE"
/kernel/linux/linux-4.19/scripts/
DMakefile.modpost13 # 1) Find all modules from the files listed in $(MODVERDIR)/
33 # Step 4 is solely used to allow module versioning in external modules,
38 # KBUILD_MODPOST_NOFINAL can be set to skip the final link of modules.
46 # When building external modules load the Kbuild file to retrieve EXTRA_SYMBOLS info
63 # Step 1), find all modules listed in $(MODVERDIR)/
66 modules := $(patsubst %.o,%.ko, $(wildcard $(__modules:.ko=.o)))
69 _modpost: $(if $(KBUILD_MODPOST_NOFINAL), $(modules:.ko:.o),$(modules))
87 quiet_cmd_modpost = MODPOST $(words $(filter-out vmlinux FORCE, $^)) modules
91 __modpost: $(modules:.ko=.o) FORCE
101 $(modules:.ko=.mod.c): __modpost ;
[all …]
DMakefile.modinst3 # Installing modules
14 modules := $(patsubst %.o,%.ko,$(wildcard $(__modules:.ko=.o)))
16 PHONY += $(modules)
17 __modinst: $(modules)
20 # Don't stop modules_install if we can't sign external modules.
29 # Modules built outside the kernel source tree go into extra by default
35 $(modules):
Ddepmod.sh28 mkdir -p "$tmp_dir/lib/modules/$KERNELRELEASE"
30 if test -e "$tmp_dir/lib/modules/$KERNELRELEASE/modules.dep" -o \
31 -e "$tmp_dir/lib/modules/$KERNELRELEASE/modules.dep.bin"; then
37 symlink="$INSTALL_MOD_PATH/lib/modules/99.98.$KERNELRELEASE"
/kernel/linux/linux-5.10/scripts/package/
Dbuilddeb90 mkdir -p $pdir/lib/modules/$version/
91 ln -s /usr/src/linux-headers-$version $pdir/lib/modules/$version/build
142 …mkdir -p "$tmpdir/usr/lib/uml/modules/$version" "$tmpdir/usr/bin" "$tmpdir/usr/share/doc/$packagen…
143 cp System.map "$tmpdir/usr/lib/uml/modules/$version/System.map"
161 rm -f "$tmpdir/lib/modules/$version/build"
162 rm -f "$tmpdir/lib/modules/$version/source"
164 mv "$tmpdir/lib/modules/$version"/* "$tmpdir/usr/lib/uml/modules/$version/"
165 rmdir "$tmpdir/lib/modules/$version"
168 for module in $(find $tmpdir/lib/modules/ -name *.ko -printf '%P\n'); do
169 module=lib/modules/$module
[all …]
/kernel/linux/linux-4.19/scripts/package/
Dbuilddeb71 mkdir -p "$kernel_headers_dir/lib/modules/$version/"
75 …mkdir -p "$tmpdir/usr/lib/uml/modules/$version" "$tmpdir/usr/bin" "$tmpdir/usr/share/doc/$packagen…
77 cp System.map "$tmpdir/usr/lib/uml/modules/$version/System.map"
95 rm -f "$tmpdir/lib/modules/$version/build"
96 rm -f "$tmpdir/lib/modules/$version/source"
98 mv "$tmpdir/lib/modules/$version"/* "$tmpdir/usr/lib/uml/modules/$version/"
99 rmdir "$tmpdir/lib/modules/$version"
102 for module in $(find $tmpdir/lib/modules/ -name *.ko -printf '%P\n'); do
103 module=lib/modules/$module
113 # resign stripped modules
[all …]
/kernel/linux/linux-5.10/Documentation/security/
Dlsm.rst2 Linux Security Modules: General Security Hooks for Linux
33 framework could then be used by loadable kernel modules to implement any
37 The Linux Security Modules (LSM) project was started by WireX to develop
50 security modules. In particular, the LSM framework is primarily focused
51 on supporting access control modules, although future development is
54 the infrastructure to support security modules. The LSM framework is
63 It also adds functions for registering security modules.
65 of security modules that are active on the system.
69 the framework or by the individual security modules that use it.
87 ``include/linux/shm.h`` as appropriate) to allow the security modules to
[all …]
/kernel/linux/linux-4.19/drivers/media/platform/davinci/
DKconfig15 be two modules called vpif.ko and vpif_display.ko
30 be two modules called vpif.ko and vpif_capture.ko
40 with decoder modules such as TVP5146 over BT656 or
46 be three modules called vpfe_capture.ko, vpss.ko and dm644x_ccdc.ko
56 with decoder modules such as TVP5146 over BT656 or
62 be three modules called vpfe_capture.ko, vpss.ko and dm355_ccdc.ko
76 be three modules called vpfe_capture.ko, vpss.ko and isif.ko
90 be five modules created called vpss.ko, vpbe.ko, vpbe_osd.ko,
/kernel/linux/linux-5.10/drivers/media/platform/davinci/
DKconfig16 be two modules called vpif.ko and vpif_display.ko
31 be two modules called vpif.ko and vpif_capture.ko
41 with decoder modules such as TVP5146 over BT656 or
47 be three modules called vpfe_capture.ko, vpss.ko and dm644x_ccdc.ko
57 with decoder modules such as TVP5146 over BT656 or
63 be three modules called vpfe_capture.ko, vpss.ko and dm355_ccdc.ko
77 be three modules called vpfe_capture.ko, vpss.ko and isif.ko
91 be five modules created called vpss.ko, vpbe.ko, vpbe_osd.ko,
/kernel/linux/linux-4.19/lib/
DKconfig78 modules require CRC-CCITT functions, but a module built outside
79 the kernel tree does. Such modules that use library CRC-CCITT
86 modules require CRC16 functions, but a module built outside
87 the kernel tree does. Such modules that use library CRC16
103 modules require CRC ITU-T V.41 functions, but a module built outside
104 the kernel tree does. Such modules that use library CRC ITU-T V.41
113 modules require CRC32/CRC32c functions, but a module built outside
114 the kernel tree does. Such modules that use library CRC32/CRC32c
177 modules require CRC64 functions, but a module built outside
178 the kernel tree does. Such modules that use library CRC64
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/LSM/
Dindex.rst8 loadable kernel modules. Instead, they are selectable at build-time via
20 The Linux capabilities modules will always be included. This may be
21 followed by any number of "minor" modules and at most one "major" module.
25 A list of the active security modules can be found by reading
29 be first, followed by any "minor" modules (e.g. Yama) and then
32 Process attributes associated with "major" security modules should
37 in ``/proc/.../attr`` remain as legacy interfaces for modules that provide
/kernel/linux/linux-5.10/drivers/iio/common/
DMakefile3 # Makefile for the IIO common modules.
4 # Common modules contains modules, which can be shared among multiple
5 # IIO modules. For example if the trigger processing is common for
6 # multiple IIO modules then this can be moved to a common module
/kernel/linux/linux-4.19/drivers/iio/common/
DMakefile3 # Makefile for the IIO common modules.
4 # Common modules contains modules, which can be shared among multiple
5 # IIO modules. For example if the trigger processing is common for
6 # multiple IIO modules then this can be moved to a common module
/kernel/liteos_a/kernel/extended/hook/include/
Dlos_hook_types.h52 …/* Hook types supported by memory modules */ …
59 …/* Hook types supported by event modules */ …
66 …/* Hook types supported by queue modules */ …
73 …/* Hook types supported by semaphore modules */ …
79 …/* Hook types supported by mutex modules */ …
84 …/* Hook types supported by task modules */ …
93 …/* Hook types supported by interrupt modules */ …
97 …/* Hook types supported by swtmr modules */ …
103 …/* Hook types supported by liteipc modules */ …
113 …/* Hook types supported by usr modules */ …

12345678910>>...111