Searched full:module (Results 1 – 25 of 857) sorted by relevance
12345678910>>...35
| /Documentation/ABI/stable/ |
| D | sysfs-module | 1 What: /sys/module
3 The /sys/module tree consists of the following structure:
5 /sys/module/MODULENAME
6 The name of the module that is in the kernel. This
7 module name will always show up if the module is loaded as a
8 dynamic module. If it is built directly into the kernel, it
15 /sys/module/MODULENAME/parameters
17 individual parameters of the module that are able to be
18 changed at runtime. See the individual module
28 /sys/module/MODULENAME/refcnt
[all …]
|
| /Documentation/scsi/ |
| D | megaraid.txt | 1 Notes on Management Module
10 the controllers uniformly. Hence it is logical to have a single module that
20 iv. Applications have to interface with only module instead of
23 Currently this module (called Common Management Module) is used only to issue
24 ioctl commands. But this module is envisioned to handle all user space level
26 common module.
31 "Shared code in a third module, a "library module", is an acceptable
34 load the shared library module."
40 then perhaps you need a single small helper module (lsiioctl or some
52 The Common Management Module is implemented in megaraid_mm.[ch] files. This
[all …]
|
| D | ChangeLog.megaraid | 3 Current Version : 2.20.5.1 (scsi module), 2.20.2.6 (cmm module)
4 Older Version : 2.20.4.9 (scsi module), 2.20.2.6 (cmm module)
18 Current Version : 2.20.4.9 (scsi module), 2.20.2.6 (cmm module)
19 Older Version : 2.20.4.8 (scsi module), 2.20.2.6 (cmm module)
141 Current Version : 2.20.4.8 (scsi module), 2.20.2.6 (cmm module)
142 Older Version : 2.20.4.7 (scsi module), 2.20.2.6 (cmm module)
166 Current Version : 2.20.4.7 (scsi module), 2.20.2.6 (cmm module)
167 Older Version : 2.20.4.6 (scsi module), 2.20.2.6 (cmm module)
201 Current Version : 2.20.4.6 (scsi module), 2.20.2.6 (cmm module)
202 Older Version : 2.20.4.5 (scsi module), 2.20.2.5 (cmm module)
[all …]
|
| /Documentation/sound/ |
| D | alsa-configuration.rst | 29 Module parameters
32 The user can load modules with options. If the module supports more than
37 Module snd
40 The core ALSA module. It is used by all ALSA card drivers.
54 See `Module Autoloading Support`_ section for details.
63 Module snd-pcm-oss
66 The PCM OSS emulation module.
67 This module takes options which change the mapping of devices.
90 Module snd-rawmidi
93 This module takes options which change the mapping of devices.
[all …]
|
| /Documentation/livepatch/ |
| D | module-elf-format.rst | 2 Livepatch module Elf format
15 4.1 A livepatch module's symbol table
25 exists in the module loader, so this former approach produced redundant
26 code. So, instead of duplicating code and re-implementing what the module
27 loader can already do, livepatch leverages existing code in the module
29 livepatch reuses the apply_relocate_add() function in the module loader to
30 write relocations. The patch module Elf format described in this document
36 Since apply_relocate_add() requires access to a module's section header
45 A typical livepatch module contains patched versions of functions that can
48 since the kernel module loader cannot resolve them and will therefore
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-module | 1 What: /sys/module/pch_phub/drivers/.../pch_mac
7 What: /sys/module/pch_phub/drivers/.../pch_firmware
14 What: /sys/module/ehci_hcd/drivers/.../uframe_periodic_max
37 What: /sys/module/*/{coresize,initsize}
41 Description: Module size in bytes.
43 What: /sys/module/*/taint
47 Description: Module taint flags:
48 P - proprietary module
49 O - out-of-tree module
50 F - force-loaded module
[all …]
|
| D | sysfs-class-net-grcan | 11 or set by the module parameter grcan.enable0 and can be read at
12 /sys/module/grcan/parameters/enable0.
23 or set by the module parameter grcan.enable1 and can be read at
24 /sys/module/grcan/parameters/enable1.
34 set by the module parameter grcan.select and can be read at
35 /sys/module/grcan/parameters/select.
|
| /Documentation/devicetree/bindings/bus/ |
| D | ti-sysc.txt | 1 Texas Instruments sysc interconnect target module wrapper binding
3 Texas Instruments SoCs can have a generic interconnect target module
6 is mostly used for interaction between module and PRCM. It participates
10 Each interconnect target module can have one or more devices connected to
12 module clocks, idle modes and interconnect level resets for the module.
16 target module and typically are named REVISION, SYSCONFIG and SYSSTATUS.
43 target module in question such as revision, sysc and syss
46 interconnect target module in question such as
49 - ranges shall contain the interconnect target module IO range
51 by the interconnect target module, the ranges may include
[all …]
|
| /Documentation/networking/ |
| D | lapb-module.txt | 1 The Linux LAPB Module Interface 1.3
7 The LAPB module will be a separately compiled module for use by any parts of
9 defines the interfaces to, and the services provided by this module. The
10 term module in this context does not imply that the LAPB module is a
11 separately loadable module, although it may be. The term module is used in
14 The interface to the LAPB module consists of functions to the module,
15 callbacks from the module to indicate important state changes, and
16 structures for getting and setting information about the module.
28 module and is not for use.
35 of the LAPB module.
[all …]
|
| D | ipv6.txt | 2 Options for the ipv6 module are supplied as parameters at load time.
4 Module options may be given as command line arguments to the insmod
9 The available ipv6 module parameters are listed below. If a parameter
16 Specifies whether to load the IPv6 module, but disable all
17 its functionality. This might be used when another module
18 has a dependency on the IPv6 module being loaded, but no
|
| /Documentation/kbuild/ |
| D | modules.rst | 5 This document describes how to build an out-of-tree kernel module.
15 === 3. Creating a Kbuild File for an External Module
24 === 5. Module Installation
27 === 6. Module Versioning
30 --- 6.3 Symbols From Another External Module
48 external module should supply a makefile that hides most of the
49 complexity, so one only has to type "make" to build the module. This is
68 NOTE: "modules_prepare" will not build Module.symvers even if
70 executed to make module versioning work.
75 The command to build an external module is::
[all …]
|
| /Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 7 This small document introduces how to test DMA drivers using dmatest module.
18 Part 1 - How to build the test module
26 be built as module or inside kernel. Let's consider those cases.
28 Part 2 - When dmatest is built as a module
38 % echo 2000 > /sys/module/dmatest/parameters/timeout
39 % echo 1 > /sys/module/dmatest/parameters/iterations
40 % echo dma0chan0 > /sys/module/dmatest/parameters/channel
41 % echo 1 > /sys/module/dmatest/parameters/run
50 % echo 2000 > /sys/module/dmatest/parameters/timeout
51 % echo 1 > /sys/module/dmatest/parameters/iterations
[all …]
|
| /Documentation/admin-guide/LSM/ |
| D | index.rst | 2 Linux Security Module Usage
5 The Linux Security Module (LSM) framework provides a mechanism for
7 "module" is a bit of a misnomer since these extensions are not actually
21 followed by any number of "minor" modules and at most one "major" module.
27 will always include the capability module. The list reflects the
28 order in which checks are made. The capability module will always
30 the one "major" module (e.g. SELinux) if there is one configured.
34 A security module may maintain a module specific subdirectory there,
35 named after the module. ``/proc/.../attr/smack`` is provided by the Smack
36 security module and contains all its special files. The files directly
|
| /Documentation/admin-guide/ |
| D | module-signing.rst | 1 Kernel module signing facility
7 .. - Configuring module signing.
21 The kernel module signing facility cryptographically signs modules during
22 installation and then checks the signature upon loading the module. This
24 or modules signed with an invalid key. Module signing increases security by
25 making it harder to load a malicious module into the kernel. The module
38 Configuring module signing
41 The module signing facility is enabled by going to the
42 :menuselection:`Enable Loadable Module Support` section of
45 CONFIG_MODULE_SIG "Module signature verification"
[all …]
|
| D | dynamic-debug-howto.rst | 31 - module name
64 # filename:lineno [module]function flags format
65 …ult/net/sunrpc/svc_rdma.c:323 [svcxprt_rdma]svc_rdma_cleanup =_ "SVCRDMA Module Removed, deregiste…
87 # filename:lineno [module]function flags format
135 'module' string |
169 module
170 The given string is compared against the module name
171 of each callsite. The module name is the string as
175 module sunrpc
176 module nfsd
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | meson-ao-cec.txt | 3 The Amlogic Meson AO-CEC module is present is Amlogic SoCs and its purpose is
8 For GXBB, GXL, GXM, G12A and SM1 (AO_CEC_A module) :
10 For G12A (AO_CEC_B module) :
12 For SM1 (AO_CEC_B module) :
21 For GXBB, GXL, GXM, G12A and SM1 (AO_CEC_A module) :
23 For G12A, SM1 (AO_CEC_B module) :
|
| /Documentation/security/ |
| D | lsm.rst | 35 migrating the Linux capabilities code into such a module.
44 of the framework and the example capabilities security module provided
57 module, with the system defaulting to the traditional superuser logic.
58 This capabilities module is discussed further in
59 `LSM Capabilities Module <#cap>`__.
110 hooks, but a security module is free to implement per-process hooks
114 module.
117 provided by a dummy security module that provides traditional superuser
119 ``security/security.c``) is provided to allow a security module to set
122 security_ops to the dummy module hooks. This mechanism is used to set
[all …]
|
| /Documentation/devicetree/bindings/rtc/ |
| D | trivial-rtc.yaml | 23 # AB-RTCMC-32.768kHz-B5ZE-S3: Real Time Clock/Calendar Module with I2C Interface
25 # AB-RTCMC-32.768kHz-EOZ9: Real Time Clock/Calendar Module with I2C Interface
33 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
35 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE with Battery Backed RAM
37 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
45 # Real Time Clock Module with I2C-Bus
47 # Real Time Clock Module with I2C-Bus
55 # Real-time Clock Module
|
| /Documentation/devicetree/bindings/crypto/ |
| D | omap-des.txt | 1 OMAP SoC DES crypto Module
6 - ti,hwmods: Name of the hwmod associated with the DES module
7 - reg : Offset and length of the register set for the module
8 - interrupts : the interrupt-specifier for the DES module
9 - clocks : A phandle to the functional clock node of the DES module
|
| D | samsung-sss.txt | 1 Samsung SoC SSS (Security SubSystem) module
3 The SSS module in S5PV210 SoC supports the following:
11 The SSS module in Exynos4 (Exynos4210) and
25 - reg : Offset and length of the register set for the module
26 - interrupts : interrupt specifiers of SSS module interrupts (one feed
|
| /Documentation/core-api/ |
| D | symbol-namespaces.rst | 29 its configuration, reject loading the module or warn about a missing import.
54 and kernel/module.c make use the namespace at build time or module load time,
92 load the module. The module code is required to use the macro MODULE_IMPORT_NS
93 for the namespaces it uses symbols from. E.g. a module using the
99 This will create a `modinfo` tag in the module for each imported namespace.
100 This has the side effect, that the imported namespaces of a module can be
109 It is advisable to add the MODULE_IMPORT_NS() statement close to other module
116 At module loading time (e.g. `insmod`), the kernel will check each symbol
117 referenced from the module for its availability and whether the namespace it
118 might be exported to has been imported by the module. The default behaviour of
[all …]
|
| /Documentation/sound/cards/ |
| D | joystick.rst | 18 independent module (ns558). Meanwhile, the ALSA PCI drivers have the
25 loading the module.
31 For PCI cards, the joystick is enabled when the appropriate module
35 changed, however, to the static module options because of the system
41 Driver Module Option Available Values
67 additional modules. Load the corresponding module to add the gameport
71 Driver Additional Module
82 support, so you don't have to load ns558 module. Just load "joydev"
83 and the appropriate adapter module (e.g. "analog").
90 Instead, you need to load "ns558" module in addition to "joydev" and
[all …]
|
| /Documentation/devicetree/bindings/arm/omap/ |
| D | ctrl.txt | 1 OMAP Control Module bindings
3 Control Module contains miscellaneous features under it based on SoC type.
5 described in [1]. Typically some clock nodes are also under control module.
7 control module driver itself.
30 - reg: Contains Control Module register address range
34 - clocks: clocks for this module
35 - clockdomains: clockdomains for this module
|
| /Documentation/i2c/ |
| D | i2c-stub.rst | 8 This module is a very simple fake I2C/SMBus driver. It implements six
12 You need to provide chip addresses as a module parameter when loading this
15 No hardware is needed nor associated with this module. It will accept write
27 module parameter.
35 1. load this module
37 3. load the target chip driver module
65 If you spam it hard enough, printk can be lossy. This module really wants
|
| /Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,bcm2835.txt | 45 Raspberry Pi Compute Module
47 compatible = "raspberrypi,compute-module", "brcm,bcm2835";
49 Raspberry Pi Compute Module 3
51 compatible = "raspberrypi,3-compute-module", "brcm,bcm2837";
53 Raspberry Pi Compute Module 3 Lite
55 compatible = "raspberrypi,3-compute-module-lite", "brcm,bcm2837";
|
12345678910>>...35