Searched +full:system +full:- +full:on +full:- +full:module (Results 1 – 25 of 344) sorted by relevance
12345678910>>...14
| /Documentation/devicetree/bindings/phy/ |
| D | ti-phy.txt | 6 - compatible: Should be one of
7 "ti,control-phy-otghs" - if it has otghs_control mailbox register as on OMAP4.
8 "ti,control-phy-usb2" - if it has Power down bit in control_dev_conf register
9 e.g. USB2_PHY on OMAP5.
10 "ti,control-phy-pipe3" - if it has DPLL and individual Rx & Tx power control
11 e.g. USB3 PHY and SATA PHY on OMAP5.
12 "ti,control-phy-pcie" - for pcie to support external clock for pcie and to
15 "ti,control-phy-usb2-dra7" - if it has power down register like USB2 PHY on
17 "ti,control-phy-usb2-am437" - if it has power down register like USB2 PHY on
19 - reg : register ranges as listed in the reg-names property
[all …]
|
| /Documentation/networking/ |
| D | lapb-module.txt | 1 The Linux LAPB Module Interface 1.3
5 Changed (Henner Eisen, 2000-10-29): int return value for data_indication()
7 The LAPB module will be a separately compiled module for use by any parts of
8 the Linux operating system that require a LAPB service. This document
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.
[all …]
|
| /Documentation/driver-api/serial/ |
| D | rocket.rst | 5 Device Driver for the Linux Operating System
9 ----------------
13 high-speed serial ports or modems. This driver supports up to a combination
18 The driver can also be installed as an external module using the usual
19 "make;make install" routine. This external module driver, obtainable
22 into them. Installations instructions for the external module
26 this driver in module form.
29 switches on the board. See the section "ISA Rocketport Boards" below for
30 information on how to set the DIP switches.
32 You pass the I/O port to the driver using the following module parameters:
[all …]
|
| /Documentation/admin-guide/ |
| D | ras.rst | 10 Reliability, Availability and Serviceability (RAS) is a concept used on
14 is the probability that a system will produce correct outputs.
20 is the probability that a system is operational at a given time
27 is the simplicity and speed with which a system can be repaired or
30 * Generally measured on Mean Time Between Repair (MTBR)
33 -------------
35 In order to reduce systems downtime, a system should be capable of detecting
38 the system administrator to take the action of replacing a component before
39 it causes data loss or system downtime.
47 Self-Monitoring, Analysis and Reporting Technology (SMART).
[all …]
|
| D | module-signing.rst | 1 Kernel module signing facility
2 ------------------------------
6 .. - Overview.
7 .. - Configuring module signing.
8 .. - Generating signing keys.
9 .. - Public keys in the kernel.
10 .. - Manually signing modules.
11 .. - Signed modules and stripping.
12 .. - Loading signed modules.
13 .. - Non-valid signatures and unsigned modules.
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm-boards | 2 -----------------------------------------------------------------------------
3 ARM's oldest Linux-supported platform with connectors for different core
7 compatible = "arm,integrator-ap"; /* Application Platform */
8 compatible = "arm,integrator-cp"; /* Compact Platform */
10 FPGA type interrupt controllers, see the versatile-fpga-irq binding doc.
14 - core-module: the root node to the Integrator platforms must have
15 a core-module with regs and the compatible string
16 "arm,core-module-integrator"
17 - external-bus-interface: the root node to the Integrator platforms
19 compatible-string "arm,external-bus-interface"
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | twl4030-power.txt | 1 Texas Instruments TWL family (twl4030) reset and power management module
3 The power management module inside the TWL family provides several facilities
5 binding only supports the complete shutdown of the system after poweroff.
8 - compatible : must be one of the following
9 "ti,twl4030-power"
10 "ti,twl4030-power-reset"
11 "ti,twl4030-power-idle"
12 "ti,twl4030-power-idle-osc-off"
14 The use of ti,twl4030-power-reset is recommended at least on
17 When using ti,twl4030-power-idle, the TI recommended configuration
[all …]
|
| /Documentation/security/ |
| D | lsm.rst | 17 about Security-Enhanced Linux (SELinux) at the 2.5 Linux Kernel Summit.
18 SELinux is an implementation of flexible and fine-grained
31 operations on kernel objects and a set of opaque security fields in
35 migrating the Linux capabilities code into such a module.
40 individuals, including Greg Kroah-Hartman and James Morris, to develop a
44 of the framework and the example capabilities security module provided
52 on supporting access control modules, although future development is
57 module, with the system defaulting to the traditional superuser logic.
58 This capabilities module is discussed further in
59 `LSM Capabilities Module <#cap>`__.
[all …]
|
| /Documentation/x86/ |
| D | intel_txt.rst | 6 Technology (Intel(R) TXT), defines platform-level enhancements that
13 - Provides dynamic root of trust for measurement (DRTM)
14 - Data protection in case of improper shutdown
15 - Measurement and verification of launched environment
18 non-vPro systems. It is currently available on desktop systems
19 based on the Q35, X38, Q45, and Q43 Express chipsets (e.g. Dell
20 Optiplex 755, HP dc7800, etc.) and mobile systems based on the GM45,
30 - LinuxTAG 2008:
31 http://www.linuxtag.org/2008/en/conf/events/vp-donnerstag.html
33 - TRUST2008:
[all …]
|
| /Documentation/networking/device_drivers/cirrus/ |
| D | cs89x0.txt | 3 ----
26 1.3 System Requirements
30 2.1 CS8900-based Adapter Configuration
31 2.2 CS8920-based Adapter Configuration
33 3.0 LOADING THE DRIVER AS A MODULE
36 4.1 Compiling the Driver as a Loadable Module
43 5.2.1 Diagnostic Self-Test
62 The CS8900-based ISA Ethernet Adapters from Cirrus Logic follow
63 IEEE 802.3 standards and support half or full-duplex operation in ISA bus
64 computers on 10 Mbps Ethernet networks. The adapters are designed for operation
[all …]
|
| /Documentation/livepatch/ |
| D | livepatch.rst | 12 4. Livepatch module
15 5. Livepatch life-cycle
28 There are many situations where users are reluctant to reboot a system. It may
29 be because their system is performing complex scientific computations or under
31 users want to also have a stable and secure system. Livepatching gives users
33 functions without a system reboot.
43 - The kernel probes are the most generic. The code can be redirected by
46 - The function tracer calls the code from a predefined location that is
48 compiler using the '-pg' gcc option.
50 - Livepatching typically needs to redirect the code at the very beginning
[all …]
|
| /Documentation/admin-guide/LSM/ |
| D | apparmor.rst | 10 from user space. Tasks on the system that do not have a profile defined for
19 If AppArmor should be selected as the default security module then set::
26 If AppArmor is not the default security module it can be enabled by passing
27 ``security=apparmor`` on the kernel's command line.
29 If AppArmor is the default security module it can be disabled by passing
30 ``apparmor=0, security=XXXX`` (where ``XXXX`` is valid security module), on the
40 Documentation can be found on the wiki, linked below.
45 Mailing List - apparmor@lists.ubuntu.com
47 Wiki - http://wiki.apparmor.net
49 User space tools - https://gitlab.com/apparmor
[all …]
|
| 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
8 loadable kernel modules. Instead, they are selectable at build-time via
9 CONFIG_DEFAULT_SECURITY and can be overridden at boot-time via the
17 specific changes to system operation when these tweaks are not available
21 followed by any number of "minor" modules and at most one "major" module.
22 For more details on capabilities, see ``capabilities(7)`` in the Linux
23 man-pages project.
27 will always include the capability module. The list reflects the
[all …]
|
| /Documentation/filesystems/ |
| D | romfs.txt | 1 ROMFS - ROM FILE SYSTEM
7 file system which doesn't take up useful memory from the router
11 defunct) filesystems, compiled as module need more than 20000 bytes,
15 nfs module with nfsroot is about 57K. Furthermore, as a bit unfair
19 To create such a file system, you'll need a user program named
20 genromfs. It is available on http://romfs.sourceforge.net/
22 As the name suggests, romfs could be also used (space-efficiently) on
23 various read-only media, like (E)EPROM disks if someone will have the
27 which has only this filesystem linked in, and then can load any module
28 later, with the current module utilities. It can also be used to run
[all …]
|
| D | gfs2.txt | 1 Global File System
2 ------------------
6 GFS is a cluster file system. It allows a cluster of computers to
9 file system, but also uses a lock module to allow the computers coordinate
10 their I/O so file system consistency is maintained. One of the nifty
11 features of GFS is perfect consistency -- changes made to the file system
12 on one machine show up immediately on all other machines in the cluster.
14 GFS uses interchangeable inter-node locking mechanisms, the currently
17 lock_nolock -- allows gfs to be used as a local file system
19 lock_dlm -- uses a distributed lock manager (dlm) for inter-node locking
[all …]
|
| /Documentation/virt/kvm/ |
| D | halt-polling.txt | 1 The KVM halt polling system
4 The KVM halt polling system provides a feature within KVM whereby the latency
12 very quickly by at least saving us a trip through the scheduler, normally on
13 the order of a few micro-seconds, although performance benefits are workload
15 interval or some other task on the runqueue is runnable the scheduler is
16 invoked. Thus halt polling is especially useful on workloads with very short
24 The powerpc kvm-hv specific case is implemented in:
32 as the halt polling interval, is increased and decreased based on the perceived
36 kvm_vcpu->halt_poll_ns
38 or in the case of powerpc kvm-hv, in the vcore struct:
[all …]
|
| /Documentation/powerpc/ |
| D | hvcs.rst | 22 2. System Requirements
24 3.1 Built-in:
25 3.2 Module:
38 space applications access to the system consoles of logically partitioned
39 operating systems (Linux and AIX) running on the same partitioned Power5
40 ppc64 system. Physical hardware consoles per partition are not practical
41 on this hardware so system consoles are accessed by this driver using
44 2. System Requirements:
48 build and run on kernels of this version or later.
50 This driver was written to operate solely on IBM Power5 ppc64 hardware
[all …]
|
| /Documentation/ |
| D | IPMI.txt | 8 standard for controlling intelligent devices that monitor a system.
9 It provides for dynamic discovery of sensors in the system and the
12 standardized database for field-replaceable units (FRUs) and a watchdog
16 system (called a Baseboard Management Controller, or BMC) and
17 management software that can use the IPMI system.
25 -------------
28 things to have it work right depending on your hardware. Most of
32 No matter what, you must pick 'IPMI top-level message handler' to use
33 IPMI. What you do beyond that depends on your needs and hardware.
35 The message handler does not provide any user-level interfaces.
[all …]
|
| /Documentation/scsi/ |
| D | ChangeLog.megaraid | 1 Release Date : Thu Nov 16 15:32:35 EST 2006 -
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)
7 Send SYNC command on loading.
9 and re-initialize its internal RAID structure.
14 2. Authors email-id domain name changed from lsil.com to lsi.com.
17 Release Date : Fri May 19 09:31:45 EST 2006 - Seokmann Ju <sju@lsil.com>
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)
22 Customer reported "garbage in file on x86_64 platform".
[all …]
|
| /Documentation/admin-guide/cifs/ |
| D | introduction.rst | 5 This is the client VFS module for the SMB3 NAS protocol as well
6 as for older dialects such as the Common Internet File System (CIFS)
13 SMB3.1.1 are supported by the CIFS VFS module. The SMB3 protocol
24 The intent of this module is to provide the most advanced network
25 file system function for SMB3 compliant servers, including advanced
27 POSIX compliance, secure per-user session establishment, encryption,
39 https://git.samba.org/?p=cifs-utils.git
43 git://git.samba.org/cifs-utils.git
47 For more information on the module see the project wiki page at
|
| /Documentation/infiniband/ |
| D | user_verbs.rst | 5 The ib_uverbs module, built by enabling CONFIG_INFINIBAND_USER_VERBS,
10 https://github.com/linux-rdma/rdma-core, is required. libibverbs contains a
11 device-independent API for using the ib_uverbs interface.
12 libibverbs also requires appropriate device-dependent kernel and
14 a Mellanox HCA, you will need the ib_mthca kernel module and the
17 User-kernel communication
24 system call or context switch into the kernel.
26 Commands are sent to the kernel via write()s on these device files.
29 contain a 64-bit field used to pass a pointer to an output buffer.
31 system call.
[all …]
|
| /Documentation/devicetree/bindings/arm/omap/ |
| D | omap.txt | 5 On top of that an omap_device is created to extend the platform_device
11 to move data from hwmod to device-tree representation.
15 - compatible: Every devices present in OMAP SoC should be in the
17 - ti,hwmods: list of hwmod names (ascii strings), that comes from the OMAP
22 - ti,no_idle_on_suspend: When present, it prevents the PM to idle the module
24 - ti,no-reset-on-init: When present, the module should not be reset at init
25 - ti,no-idle-on-init: When present, the module should not be idled at init
26 - ti,no-idle: When present, the module is never allowed to idle.
31 compatible = "ti,omap4-spinlock";
37 - General Purpose devices
[all …]
|
| /Documentation/driver-api/usb/ |
| D | hotplug.rst | 8 In hotpluggable busses like USB (and Cardbus PCI), end-users plug devices
9 into the bus with power on. In most cases, users expect the devices to become
10 immediately usable. That means the system must do many things, including:
12 - Find a driver that can handle the device. That may involve
13 loading a kernel module; newer drivers can use module-init-tools
16 - Bind a driver to that device. Bus frameworks do that using a
19 - Tell other subsystems to configure the new device. Print
21 partitions mounted, and so on. In some cases these will
22 be driver-specific actions.
30 Those triggered actions must support a system's administrative policies;
[all …]
|
| /Documentation/admin-guide/hw-vuln/ |
| D | multihit.rst | 8 or cache type. A malicious guest running on a virtualized system can
13 -------------------
15 Variations of this erratum are present on most Intel Core and Xeon processor
16 models. The erratum is not present on:
18 - non-Intel processors
20 - Some Atoms (Airmont, Bonnell, Goldmont, GoldmontPlus, Saltwell, Silvermont)
22 - Intel processors that have the PSCHANGE_MC_NO bit set in the
27 ------------
32 CVE-2018-12207 Machine Check Error Avoidance on Page Size Change
37 -------
[all …]
|
| /Documentation/locking/ |
| D | locktorture.rst | 8 The CONFIG LOCK_TORTURE_TEST config option provides a kernel module
9 that runs torture tests on core kernel locking primitives. The kernel
10 module, 'locktorture', may be built after the fact on the running
13 grepping for "torture"). The test is started when the module is loaded,
14 and stops when the module is unloaded. This program is based on how RCU
19 different critical region behaviors. The amount of contention on the lock
24 Module Parameters
27 This module has the following parameters:
30 Locktorture-specific
31 --------------------
[all …]
|
12345678910>>...14