Searched refs:Protocol (Results 1 – 25 of 188) sorted by relevance
12345678
1 Key-agreement Protocol Primitives (KPP) Cipher Algorithm Definitions7 Key-agreement Protocol Primitives (KPP) Cipher API11 :doc: Generic Key-agreement Protocol Primitives API16 Key-agreement Protocol Primitives (KPP) Cipher Request Handle
32 * CAIF Core Protocol Implementation47 ! +------+ <- CAIF Core Protocol63 CAIF Core Protocol Layer69 The architecture is inspired by the design patterns "Protocol Layer" and70 "Protocol Packet".91 The CAIF protocol can be divided into two parts: Support functions and Protocol94 - CFPKT CAIF Packet. Implementation of CAIF Protocol Packet. The98 The CAIF Protocol implementation contains:100 - CFCNFG CAIF Configuration layer. Configures the CAIF Protocol192 The CAIF Protocol relies on a loss-less link layer without implementing
3 # Layer Two Tunneling Protocol (L2TP)7 tristate "Layer Two Tunneling Protocol (L2TP)"12 Layer Two Tunneling Protocol54 Layer Two Tunneling Protocol Version 358 The Layer Two Tunneling Protocol (L2TP) provides a dynamic62 tunneling Point-to-Point Protocol (PPP) [RFC1661] sessions.96 The Layer 2 Tunneling Protocol, Version 3 (L2TPv3) can be
4 The Linux/x86 Boot Protocol20 Protocol 2.00 (Kernel 1.3.73) Added bzImage and initrd support, as26 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 possible38 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 of46 Protocol 2.07 (Kernel 2.6.24) Added paravirtualised boot protocol.50 Protocol 2.08 (Kernel 2.6.26) Added crc32 checksum and ELF format[all …]
3 tristate "The DCCP Protocol"6 Datagram Congestion Control Protocol (RFC 4340)10 The Datagram Congestion Control Protocol (DCCP) is a transport
22 Protocol Arbiter, which manage a related pool of memory devices. A system23 may have a single Protocol Arbiter or multiple Protocol Arbiters.26 Domains and Protocol Arbiters. In the simplest version of the system, the28 and a single Protocol Arbiter.
30 L2CAP (Logical Link Control and Adaptation Protocol)31 SMP (Security Manager Protocol) on LE (Low Energy) links34 RFCOMM Module (RFCOMM Protocol) 35 BNEP Module (Bluetooth Network Encapsulation Protocol)36 CMTP Module (CAPI Message Transport Protocol)37 HIDP Module (Human Interface Device Protocol)
3 tristate "InfiniBand SCSI RDMA Protocol"7 Support for the SCSI RDMA Protocol over InfiniBand. This
3 tristate "Intel(R) Ethernet Protocol Driver for RDMA"11 This is an Intel(R) Ethernet Protocol Driver for RDMA driver
3 tristate "InfiniBand SCSI RDMA Protocol target support"7 Support for the SCSI RDMA Protocol (SRP) Target driver. The
16 You can't use this driver and the HIDBP (Boot Protocol) keyboard48 menu "USB HID Boot Protocol drivers"57 to use the keyboard in its limited Boot Protocol mode instead.73 to use the mouse in its limited Boot Protocol mode instead.
7 BNEP (Bluetooth Network Encapsulation Protocol) is Ethernet21 bool "Protocol filter support"
7 title: i.MX SCU Client Device Node - Power domain bindings based on SCU Message Protocol14 Power domain bindings based on SCU Message Protocol
2 ALPS Touchpad Protocol51 Protocol versions 3 and 4 have a command mode that is used to read and write104 ALPS Absolute Mode - Protocol Version 1116 ALPS Absolute Mode - Protocol Version 2128 Protocol Version 2 DualPoint devices send standard PS/2 mouse packets for154 ALPS Absolute Mode - Protocol Version 3202 ALPS Absolute Mode - Protocol Version 4205 Protocol version 4 has an 8-byte packet format::246 ALPS Absolute Mode - Protocol Version 5248 This is basically Protocol Version 3 but with different logic for packet[all …]
3 tristate "IMX DSP Protocol driver"14 bool "IMX SCU Protocol driver"
45 Data Link Protocol 048 Flow Control Protocol 075 Data Link Protocol 078 Flow Control Protocol 0
11 Firmware Management Protocol. To support Firmware Management by the AP, the13 Firmware Management Protocol CPort within it.25 ; (Mandatory) Firmware Management Protocol on CPort 130 ; (Optional) Firmware Download Protocol on CPort 240 ; (Optional) Component Authentication Protocol (CAP) on CPort 449 The Firmware Management Protocol interacts with Userspace using the character186 The Component Authentication Protocol interacts with Userspace using the309 The Firmware Download Protocol uses the existing Linux Kernel's Firmware class
23 bool "GVRP (GARP VLAN Registration Protocol) support"33 bool "MVRP (Multiple VLAN Registration Protocol) support"
29 Adds support for the CCM mode Protocol crypto driver for43 Adds support for the Temporal Key Integrity Protocol for
24 tristate "Raw CAN Protocol (raw access with CAN-ID filtering)"34 tristate "Broadcast Manager CAN Protocol (with content filtering)"65 segmentation is needed to transport longer Protocol Data Units (PDU)
11 tristate "B.A.T.M.A.N. Advanced Meshing Protocol"28 discovery protocol (Echo Location Protocol, ELP) and a new OGM29 Protocol OGMv2 for flooding protocol information through the
3 # Parallel Line Internet Protocol (PLIP) network device configuration10 PLIP (Parallel Line Internet Protocol) is used to create a
6 CMTP (CAPI Message Transport Protocol) is a transport layer
7 HIDP (Human Interface Device Protocol) is a transport layer
15 This provides ARM SCMI Protocol based IIO device.