Searched full:protocol (Results 1 – 25 of 331) sorted by relevance
12345678910>>...14
| /Documentation/netlabel/ |
| D | introduction.rst | 15 is composed of three main components, the protocol engines, the communication
18 Protocol Engines
21 The protocol engines are responsible for both applying and retrieving the
23 security attributes and those on the host are required then the protocol
25 refrain from calling the protocol engines directly, instead they should use
28 Detailed information about each NetLabel protocol engine can be found in this
36 protocol built on top of the Generic NETLINK transport mechanism. The exact
44 The purpose of the NetLabel security module API is to provide a protocol
45 independent interface to the underlying NetLabel protocol engines. In addition
46 to protocol independence, the security module API is designed to be completely
|
| D | cipso_ipv4.rst | 2 NetLabel CIPSO/IPv4 Protocol Engine
12 The NetLabel CIPSO/IPv4 protocol engine is based on the IETF Commercial
22 The CIPSO/IPv4 protocol engine applies the CIPSO IP option to packets by
34 The CIPSO/IPv4 protocol engine validates every CIPSO IP option it finds at the
44 The CIPSO/IPv4 protocol engine contains a mechanism to translate CIPSO security
56 CIPSO/IPv4 protocol engine supports this caching mechanism.
|
| /Documentation/media/uapi/rc/ |
| D | rc-protos.rst | 11 IR is encoded as a series of pulses and spaces, using a protocol. These
14 across different devices for a given protocol.
29 how scancodes are encoded for each protocol.
34 This IR protocol uses manchester encoding to encode 14 bits. There is a
38 protocol, or the manchester BPF decoder.
184 The jvc protocol is much like nec, without the inverted values. It is
193 The sony protocol is a pulse-width encoding. There are three variants,
220 The sony protocol is a pulse-width encoding. There are three variants,
247 The sony protocol is a pulse-width encoding. There are three variants,
280 The nec protocol encodes an 8 bit address and an 8 bit command. It is
[all …]
|
| D | rc-sysfs-nodes.rst | 50 Writing "+proto" will add a protocol to the list of enabled protocols.
52 Writing "-proto" will remove a protocol from the list of enabled
59 Write fails with ``EINVAL`` if an invalid protocol combination or unknown
60 protocol name is used.
75 This value may be reset to 0 if the current protocol is altered.
91 This value may be reset to 0 if the current protocol is altered.
104 Note that protocol variants are listed, so ``nec``, ``sony``, ``rc-5``, ``rc-6``
107 Note that all protocol variants are listed.
109 The enabled wakeup protocol is shown in [] brackets.
111 Only one protocol can be selected at a time.
[all …]
|
| /Documentation/trace/ |
| D | sys-t.rst | 7 The MIPI SyS-T protocol driver can be used with STM class devices to
11 In order to use the MIPI SyS-T protocol driver with your STM device,
14 Now, you can select which protocol driver you want to use when you create
25 If the protocol name is omitted, the STM class will chose whichever
26 protocol driver was loaded first.
30 # cat /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/protocol
33 Now, with the MIPI SyS-T protocol driver, each policy node in the
35 parameters specific to the protocol:
56 can pass before we need to include a protocol (not transport, aka STP)
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-rc | 27 Writing "+proto" will add a protocol to the list of enabled
29 Writing "-proto" will remove a protocol from the list of enabled
33 Write fails with EINVAL if an invalid protocol combination or
34 unknown protocol name is used.
47 This value may be reset to 0 if the current protocol is altered.
62 This value may be reset to 0 if the current protocol is altered.
72 Note that protocol variants are listed, so "nec", "sony",
75 The enabled wakeup protocol is shown in [] brackets.
76 Only one protocol can be selected at a time.
79 Write fails with EINVAL if an invalid protocol combination or
[all …]
|
| D | configfs-usb-gadget-hid | 7 protocol - HID protocol to use
|
| D | sysfs-class-mei | 36 Description: Display the negotiated HBM protocol version.
38 The HBM protocol version negotiated
45 Description: Display the driver HBM protocol version.
47 The HBM protocol version supported by the driver.
|
| /Documentation/networking/caif/ |
| D | Linux-CAIF.txt | 10 CAIF is a MUX protocol used by ST-Ericsson cellular modems for
23 * CAIF Core Protocol Implementation
37 ! +------+ <- CAIF Core Protocol
53 CAIF Core Protocol Layer
56 CAIF Core layer implements the CAIF protocol as defined by ST-Ericsson.
57 It implements the CAIF protocol stack in a layered approach, where
59 The architecture is inspired by the design patterns "Protocol Layer" and
60 "Protocol Packet".
77 The CAIF protocol can be divided into two parts: Support functions and Protocol
80 - CFPKT CAIF Packet. Implementation of CAIF Protocol Packet. The
[all …]
|
| /Documentation/x86/ |
| D | boot.rst | 4 The Linux/x86 Boot Protocol
14 Currently, the following versions of the Linux/x86 boot protocol exist.
20 Protocol 2.00 (Kernel 1.3.73) Added bzImage and initrd support, as
26 Protocol 2.01 (Kernel 1.3.76) Added a heap overrun warning.
28 Protocol 2.02 (Kernel 2.4.0-test3-pre3) New command line protocol.
35 Protocol 2.03 (Kernel 2.4.18-pre1) Explicitly makes the highest possible
38 Protocol 2.04 (Kernel 2.6.14) Extend the syssize field to four bytes.
40 Protocol 2.05 (Kernel 2.6.20) Make protected mode kernel relocatable.
43 Protocol 2.06 (Kernel 2.6.22) Added a field that contains the size of
46 Protocol 2.07 (Kernel 2.6.24) Added paravirtualised boot protocol.
[all …]
|
| /Documentation/networking/ |
| D | sctp.txt | 6 SCTP (Stream Control Transmission Protocol) is a IP based, message oriented,
7 reliable transport protocol, with congestion control, support for
9 RFC2960 defines the core protocol. The IETF SIGTRAN working group originally
10 developed the SCTP protocol and later handed the protocol over to the
|
| D | phonet.txt | 1 Linux Phonet protocol family
7 Phonet is a packet protocol used by Nokia cellular modems for both IPC
43 protocol (much like port numbers in IP world).
89 Low-level datagram protocol
93 protocol from the PF_PHONET family. Each socket is bound to one of the
110 This protocol follows the SOCK_DGRAM connection-less semantics.
131 Phonet Pipe protocol
134 The Phonet Pipe protocol is a simple sequenced packets protocol
188 The pipe protocol provides two socket options at the SOL_PNPIPE level:
|
| /Documentation/media/uapi/cec/ |
| D | cec-intro.rst | 16 Control protocol. This protocol allows different devices connected by an
17 HDMI cable to communicate. The protocol for CEC version 1.4 is defined
24 and is based on the ancient AV.link protocol used in old SCART
25 connectors. The protocol closely resembles a crazy Rube Goldberg
27 messages, especially those part of the HEAC protocol layered on top of
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,scmi.txt | 1 System Control and Management Interface (SCMI) Message Protocol
25 protocol identifier for a given sub-node.
40 Each protocol supported shall have a sub-node with corresponding compatible
42 communication channel for a particular protocol, the 3 properties namely:
44 to that protocol.
46 Clock/Performance bindings for the clocks/OPPs based on SCMI Message Protocol
54 Power domain bindings for the power domains based on SCMI Message Protocol
64 Sensor bindings for the sensors based on SCMI Message Protocol
76 Reset signal bindings for the reset domains based on SCMI Message Protocol
147 scmi_devpd: protocol@11 {
[all …]
|
| /Documentation/driver-api/ |
| D | i2c.rst | 5 the "Inter-IC" bus, a simple bus protocol which is widely used where low
26 are functions to perform various I2C protocol operations; at this writing
29 The System Management Bus (SMBus) is a sibling protocol. Most SMBus
31 for SMBus, and it standardizes particular protocol messages and idioms.
33 SMBus controllers don't support all the protocol options that an I2C
34 controller will. There are functions to perform various SMBus protocol
|
| /Documentation/driver-api/mei/ |
| D | iamt.rst | 21 - Selective network isolation of Ethernet and IP protocol flows based
26 starting with Release 6.0) over HTTP/S or WS-Management protocol over
57 using a protocol called Intel AMT Port Forwarding Protocol (Intel APF protocol).
58 The protocol is used to maintain multiple sessions with Intel AMT from a
61 See the protocol specification in the Intel AMT Software Development Kit (SDK)
65 => "Description of the Intel AMT Port Forwarding (APF) Protocol"
|
| /Documentation/filesystems/cifs/ |
| D | cifsroot.txt | 8 support over the SMB protocol via cifs.ko.
12 network by utilizing SMB or CIFS protocol.
20 deprecated version of the protocol but it has been extended to support
22 recommended version of the protocol (SMB3) have not been fully
38 server min protocol = NT1
47 the root file system via SMB protocol.
|
| /Documentation/scsi/ |
| D | ufs.txt | 11 2.2 UFS Transport Protocol(UTP) layer
54 protocol agnostic, however SCSI has been selected as a baseline
55 protocol for versions 1.0 and 1.1 of UFS protocol layer.
67 2.2 UFS Transport Protocol(UTP) layer
79 UTP transports messages through UFS protocol information unit(UPIU).
134 This transport driver supports exchanging UFS protocol information units
144 io_hdr_v4.protocol = BSG_PROTOCOL_SCSI;
162 upiu-based protocol is available at:
|
| /Documentation/i2c/ |
| D | summary.rst | 5 I2C (pronounce: I squared C) is a protocol developed by Philips. It is a
6 slow two-wire protocol (variable speed, up to 400 kHz), with a high speed
12 SMBus (System Management Bus) is based on the I2C protocol, and is mostly
22 implement all the common SMBus protocol semantics or messages.
|
| D | smbus-protocol.rst | 2 SMBus Protocol Summary
5 The following is a summary of the SMBus protocol. It applies to
6 all revisions of the protocol (1.0, 1.1, and 2.0).
7 Certain protocol features which are not supported by
10 Some adapters understand only the SMBus (System Management Bus) protocol,
11 which is a subset from the I2C protocol. Fortunately, many devices use
16 I2C protocol). This makes it possible to use the device driver on both
21 Below is a list of SMBus protocol operations, and the functions executing
22 them. Note that the names used in the SMBus protocol specifications usually
24 single data byte, the functions using SMBus protocol operation names execute
[all …]
|
| /Documentation/crypto/ |
| D | api-kpp.rst | 1 Key-agreement Protocol Primitives (KPP) Cipher Algorithm Definitions
7 Key-agreement Protocol Primitives (KPP) Cipher API
11 :doc: Generic Key-agreement Protocol Primitives API
16 Key-agreement Protocol Primitives (KPP) Cipher Request Handle
|
| /Documentation/devicetree/bindings/sound/ |
| D | st,stm32-sai.txt | 52 - st,iec60958: support S/PDIF IEC6958 protocol for playback
53 IEC60958 protocol is not available for capture.
54 By default, custom protocol is assumed, meaning that protocol is
55 configured according to protocol defined in related DAI link node,
57 Note: ac97 protocol is not supported by SAI driver
|
| /Documentation/input/ |
| D | multi-touch-protocol.rst | 4 Multi-touch (MT) Protocol
16 document describes the multi-touch (MT) protocol which allows kernel
19 The protocol is divided into two types, depending on the capabilities of the
20 hardware. For devices handling anonymous contacts (type A), the protocol
22 devices capable of tracking identifiable contacts (type B), the protocol
26 MT protocol type A is obsolete, all kernel drivers have been
29 Protocol Usage
35 applications, the MT protocol can be implemented on top of the ST protocol
53 The main difference between the stateless type A protocol and the stateful
54 type B slot protocol lies in the usage of identifiable contacts to reduce
[all …]
|
| /Documentation/admin-guide/cifs/ |
| D | introduction.rst | 5 This is the client VFS module for the SMB3 NAS protocol as well
7 protocol which was the successor to the Server Message Block
8 (SMB) protocol, the native file sharing mechanism for most early
13 SMB3.1.1 are supported by the CIFS VFS module. The SMB3 protocol
|
| /Documentation/admin-guide/blockdev/ |
| D | paride.rst | 21 and the communication protocol provides operations for reading and writing
71 The third component of PARIDE is a set of low-level protocol drivers
109 You can actually select all the protocol modules, and allow the PARIDE
112 For the "brand-name" products listed above, here are the protocol
116 Manufacturer Model Driver Protocol
148 can find, and all protocol types that have been installed, until it finds
152 protocol identification number and, for some devices, the drive's
158 paride: bpck registered as protocol 0
159 paride: epat registered as protocol 1
162 different protocol selections. You should note these numbers as you
[all …]
|
12345678910>>...14