Searched refs:Protocol (Results 1 – 25 of 138) sorted by relevance
123456
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
23 * CAIF Core Protocol Implementation37 ! +------+ <- CAIF Core Protocol53 CAIF Core Protocol Layer59 The architecture is inspired by the design patterns "Protocol Layer" and60 "Protocol Packet".77 The CAIF protocol can be divided into two parts: Support functions and Protocol80 - CFPKT CAIF Packet. Implementation of CAIF Protocol Packet. The84 The CAIF Protocol implementation contains:86 - CFCNFG CAIF Configuration layer. Configures the CAIF Protocol172 The CAIF Protocol relies on a loss-less link layer without implementing
2 # Layer Two Tunneling Protocol (L2TP)6 tristate "Layer Two Tunneling Protocol (L2TP)"11 Layer Two Tunneling Protocol53 Layer Two Tunneling Protocol Version 357 The Layer Two Tunneling Protocol (L2TP) provides a dynamic61 tunneling Point-to-Point Protocol (PPP) [RFC1661] sessions.95 The Layer 2 Tunneling Protocol, Version 3 (L2TPv3) can be
28 L2CAP (Logical Link Control and Adaptation Protocol)29 SMP (Security Manager Protocol) on LE (Low Energy) links31 RFCOMM Module (RFCOMM Protocol) 32 BNEP Module (Bluetooth Network Encapsulation Protocol)33 CMTP Module (CAPI Message Transport Protocol)34 HIDP Module (Human Interface Device Protocol)
16 Protocol 2.00: (Kernel 1.3.73) Added bzImage and initrd support, as22 Protocol 2.01: (Kernel 1.3.76) Added a heap overrun warning.24 Protocol 2.02: (Kernel 2.4.0-test3-pre3) New command line protocol.31 Protocol 2.03: (Kernel 2.4.18-pre1) Explicitly makes the highest possible34 Protocol 2.04: (Kernel 2.6.14) Extend the syssize field to four bytes.36 Protocol 2.05: (Kernel 2.6.20) Make protected mode kernel relocatable.39 Protocol 2.06: (Kernel 2.6.22) Added a field that contains the size of42 Protocol 2.07: (Kernel 2.6.24) Added paravirtualised boot protocol.46 Protocol 2.08: (Kernel 2.6.26) Added crc32 checksum and ELF format50 Protocol 2.09: (Kernel 2.6.26) Added a field of 64-bit physical[all …]
2 tristate "The DCCP Protocol"5 Datagram Congestion Control Protocol (RFC 4340)9 The Datagram Congestion Control Protocol (DCCP) is a transport
2 tristate "InfiniBand SCSI RDMA Protocol"6 Support for the SCSI RDMA Protocol over InfiniBand. This
2 tristate "InfiniBand SCSI RDMA Protocol target support"6 Support for the SCSI RDMA Protocol (SRP) Target driver. The
6 BNEP (Bluetooth Network Encapsulation Protocol) is Ethernet20 bool "Protocol filter support"
15 You can't use this driver and the HIDBP (Boot Protocol) keyboard47 menu "USB HID Boot Protocol drivers"56 to use the keyboard in its limited Boot Protocol mode instead.72 to use the mouse in its limited Boot Protocol mode instead.
1 System Control and Power Interface (SCPI) Message Protocol17 Sensor bindings for the sensors based on SCPI Message Protocol
1 System Control and Management Interface (SCMI) Message Protocol46 Clock/Performance bindings for the clocks/OPPs based on SCMI Message Protocol54 Power domain bindings for the power domains based on SCMI Message Protocol64 Sensor bindings for the sensors based on SCMI 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 …]
46 Data Link Protocol 049 Flow Control Protocol 077 Data Link Protocol 080 Flow Control Protocol 0
22 bool "GVRP (GARP VLAN Registration Protocol) support"32 bool "MVRP (Multiple VLAN Registration Protocol) support"
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
245 buffer->Protocol[0] = 0xFF; in header_assemble()246 buffer->Protocol[1] = 'S'; in header_assemble()247 buffer->Protocol[2] = 'M'; in header_assemble()248 buffer->Protocol[3] = 'B'; in header_assemble()284 if (*(__le32 *) smb->Protocol != cpu_to_le32(0x424d53ff)) { in check_smb_hdr()286 *(unsigned int *)smb->Protocol); in check_smb_hdr()417 ((char *)&pSMBr->hdr.Protocol + data_offset); in is_valid_oplock_break()
2 # Parallel Line Internet Protocol (PLIP) network device configuration9 PLIP (Parallel Line Internet Protocol) is used to create a
22 tristate "Raw CAN Protocol (raw access with CAN-ID filtering)"32 tristate "Broadcast Manager CAN Protocol (with content filtering)"
5 CMTP (CAPI Message Transport Protocol) is a transport layer
6 HIDP (Human Interface Device Protocol) is a transport layer
23 tristate "B.A.T.M.A.N. Advanced Meshing Protocol"42 discovery protocol (Echo Location Protocol, ELP) and a new OGM43 Protocol OGMv2 for flooding protocol information through the
1 Binding for Synopsys IntelliDDR Multi Protocol Memory Controller
6 Support for the iSCSI Extensions for RDMA (iSER) Protocol
6 tristate "The SCTP Protocol"14 Stream Control Transmission Protocol
