Searched full:modules (Results 1 – 25 of 381) sorted by relevance
12345678910>>...16
| /Documentation/admin-guide/ |
| D | module-signing.rst | 10 .. - 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 …]
|
| /Documentation/kbuild/ |
| D | modules.rst | 2 Building External Modules
10 "kbuild" is the build system used by the Linux kernel. Modules must use
12 to pick up the right flags to the compiler. Functionality for building modules
14 either is similar, and all modules are initially developed and built
18 in building out-of-tree (or "external") modules. The author of an
25 How to Build External Modules
28 To build external modules, you must have a prebuilt kernel available
30 Also, the kernel must have been built with modules enabled. If you are
37 building external modules.
55 $ make -C /lib/modules/`uname -r`/build M=$PWD
[all …]
|
| D | kbuild.rst | 9 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.
25 modules.builtin.ranges
27 This file contains address offset ranges (per ELF section) for all modules
47 Additional options to the assembler (for built-in and modules).
[all …]
|
| D | reproducible-builds.rst | 79 modules being unreproducible. However, including a signing key with
80 your source would presumably defeat the purpose of signing modules.
91 Build the kernel and modules.
93 3. Create detached signatures for the modules, and publish them as
97 can either rebuild the modules or use the output of step 2.
|
| /Documentation/admin-guide/LSM/ |
| D | index.rst | 8 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
|
| /Documentation/security/ |
| D | lsm.rst | 2 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 …]
|
| /Documentation/i2c/busses/ |
| D | i2c-taos-evm.rst | 7 This is a driver for the evaluation modules for TAOS I2C/SMBus chips.
8 The modules include an SMBus master with limited capabilities, which can
9 be controlled over the serial port. Virtually all evaluation modules
38 modules:
48 practice, as these modules are meant for evaluation and testing only.
|
| /Documentation/driver-api/media/drivers/ |
| D | pvrusb2.rst | 63 To build these modules essentially amounts to just running "Make",
115 modules should have any business using this header. All external
130 pvrusb2-i2c-chips-\*.c - These modules implement the glue logic to
131 tie together and configure various I2C modules as they attach to
136 V4L, where we might encounter other possibly "challenging" modules
137 from ivtv or older kernel snapshots (or even the support modules
141 compatible commands to the I2C modules. It is here where state
143 commands that are in turn send to the various I2C modules.
146 compatible commands to the I2C modules. It is here where state
148 commands that are in turn send to the various I2C modules.
[all …]
|
| /Documentation/userspace-api/ |
| D | lsm.rst | 6 Linux Security Modules
12 Linux security modules (LSM) provide a mechanism to implement
15 The various security modules may support any of these attributes:
20 This is supported by the SELinux, Smack and AppArmor security modules.
27 This is supported by the SELinux and AppArmor security modules.
43 This is supported by the SELinux and AppArmor security modules.
|
| /Documentation/devicetree/bindings/clock/ |
| D | imx7ulp-scg-clock.yaml | 7 title: Freescale i.MX7ULP System Clock Generation (SCG) modules Clock Controller
14 Clock Generation (SCG) modules, Peripheral Clock Control (PCC)
15 modules, and Core Mode Controller (CMC)1 blocks
23 M4 clock management consists of SCG0, PCC0, PCC1, and CMC0 modules.
24 A7 clock management consists of SCG1, PCC2, PCC3, and CMC1 modules.
|
| D | imx7ulp-pcc-clock.yaml | 7 title: Freescale i.MX7ULP Peripheral Clock Control (PCC) modules Clock Controller
14 Clock Generation (SCG) modules, Peripheral Clock Control (PCC)
15 modules, and Core Mode Controller (CMC)1 blocks
23 M4 clock management consists of SCG0, PCC0, PCC1, and CMC0 modules.
24 A7 clock management consists of SCG1, PCC2, PCC3, and CMC1 modules.
|
| D | imx8ulp-cgc-clock.yaml | 14 under the control of several CGCs & PCCs modules. The CGC modules generate
|
| /Documentation/ |
| D | dontdiff | 180 modules-only.symvers
181 modules.builtin
182 modules.builtin.modinfo
183 modules.builtin.ranges
184 modules.nsdeps
185 modules.order
|
| /Documentation/core-api/ |
| D | symbol-namespaces.rst | 16 === 4 Loading Modules that use namespaced Symbols
27 kernel. As of today, modules that make use of symbols exported into namespaces,
32 limiting which modules are allowed to use these symbols.
97 modules to access this symbol. Simple tail-globs are supported.
103 will limit usage of this symbol to modules whoes name matches the given
109 In order to use symbols that are exported into namespaces, kernel modules need
132 4. Loading Modules that use namespaced Symbols
138 the kernel is to reject loading modules that don't specify sufficient imports.
140 allow loading of modules that don't satisfy this precondition, a configuration
166 in-tree modules::
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | sff,sfp.yaml | 16 - sff,sfp # for SFP modules
17 - sff,sff # for soldered down SFF modules
29 allowable by a module in the slot, in milli-Watts. Presently, modules can
37 present for SFF modules
62 present for SFF modules
69 not be present for SFF modules
|
| D | fsl,fman-muram.yaml | 13 FMan Internal memory - shared between all the FMan modules.
15 the modules.
|
| /Documentation/admin-guide/media/ |
| D | ci.rst | 65 CI modules that are supported
69 Some cards do support almost all of the available CI modules. There is
70 nothing much that can be done in order to make additional CI modules
73 Modules that have been tested by this driver at present are
|
| D | technisat.rst | 32 get rid of unnecessary modules and check this one:
34 ``Multimedia support`` => ``Customise analog and hybrid tuner modules to build``
53 => ``Customise the frontend modules to build`` ``Customise DVB frontends`` =>
99 …#) ``Multimedia support`` => ``Customise analog and hybrid tuner modules to build`` => ``Simple tu…
|
| /Documentation/scsi/ |
| D | scsi.rst | 12 Notes on using modules in the SCSI subsystem
22 loaded, and if you unload the modules, it will have to be the last one
24 will enforce the correct ordering of loading and unloading modules in
40 Adaptec. Almost all lower level drivers can be built either as modules or
|
| /Documentation/devicetree/bindings/bus/ |
| D | arm,integrator-ap-lm.yaml | 13 site for stacking up to four logic modules (LM) designed specifically for
16 module connector is described in this binding. The logic modules per se
36 description: Nodes on the Logic Module bus represent logic modules
61 /* The Logic Modules sees the Core Module 0 RAM @80000000 */
|
| /Documentation/userspace-api/ebpf/ |
| D | index.rst | 8 source code or loading kernel modules. eBPF programs can be attached to various
9 kernel subsystems, including networking, tracing and Linux security modules
|
| /Documentation/sound/designs/ |
| D | powersave.rst | 16 module option of snd-ac97-codec and snd-hda-intel modules. Specify
28 ``/sys/modules/snd_ac97_codec/parameters/power_save`` (usually as root):
31 # echo 10 > /sys/modules/snd_ac97_codec/parameters/power_save
|
| /Documentation/livepatch/ |
| D | module-elf-format.rst | 5 This document outlines the ELF format requirements that livepatch modules must follow.
31 preserved for livepatch modules (see section 5). Livepatch manages its own
43 affect modules not yet loaded at patch module load time (e.g. a patch to a
59 Livepatch modules are required to have the "livepatch" modinfo attribute.
62 Livepatch modules can be identified by users by using the 'modinfo' command
64 used by the kernel module loader to identify livepatch modules.
84 relocations to modules as well as to the kernel (vmlinux) at the
98 Since ELF information is preserved for livepatch modules (see Section 5), a
146 module that patches vmlinux and modules 9p, btrfs, ext4:**
205 loader can identify and ignore them. Livepatch modules keep these symbols
[all …]
|
| /Documentation/power/ |
| D | basic-pm-debugging.rst | 131 unloaded all modules. In that case, you may want to look in your kernel
132 configuration for the drivers that can be compiled as modules (and test again
133 with these drivers compiled as modules). You may also try to use some special
164 can try to compile more drivers as modules, so that they can be tested
166 find it by loading a half of the modules you normally use and binary searching
168 - if there are n modules loaded and the attempt to suspend and resume fails,
169 unload n/2 of the modules and try again (that would probably involve rebooting
171 - if there are n modules loaded and the attempt to suspend and resume succeeds,
172 load n/2 modules more and try again.
207 configuration and compiling more drivers as modules is not practical or some
[all …]
|
| /Documentation/bpf/ |
| D | bpf_licensing.rst | 64 Linux Kernel (while being GPLv2) allows linking of proprietary kernel modules
75 modules. BPF programs can be proprietary if they don't use "GPL only" BPF
78 Further, some BPF program types - Linux Security Modules (LSM) and TCP
81 registration step of LSM and TCP congestion control modules of the Linux
|
12345678910>>...16