Home
last modified time | relevance | path

Searched refs:protocol (Results 1 – 25 of 208) sorted by relevance

123456789

/Documentation/isdn/
DREADME.concap1 Description of the "concap" encapsulation protocol interface
5 drivers that need to process an encapsulation protocol.
6 It is assumed that the protocol interacts with a linux network device by
22 The encapsulation protocol used on top of WAN connections or permanent
28 encapsulation protocols. The encapsulation protocol is configured by a
31 depending on the currently configured encapsulation protocol.
34 protocol which is unique to the hardware type of the interface. The LAN
37 encapsulation protocol directly (usually by just providing a hard_header()
43 The configurability of the encapsulation protocol to be used
64 protocol, complexity could be reduced and maintainability could be
[all …]
DINTERFACE362 protocol. This command is issued by the LL prior to ISDN_CMD_DIAL or
370 logical or'ed with (protocol-Id << 8)
371 protocol-Id is one of the constants ISDN_PROTO_L2...
377 setting of the Layer-2-protocol.
385 current protocol-Id (one of the constants ISDN_L2_PROTO)
390 protocol. This command is issued by the LL prior to ISDN_CMD_DIAL or
398 logical or'ed with (protocol-Id << 8)
399 protocol-Id is one of the constants ISDN_PROTO_L3...
405 setting of the Layer-3-protocol.
413 current protocol-Id (one of the constants ISDN_L3_PROTO)
[all …]
/Documentation/netlabel/
Dintroduction.txt12 is composed of three main components, the protocol engines, the communication
17 The protocol engines are responsible for both applying and retrieving the
19 security attributes and those on the host are required then the protocol
21 refrain from calling the protocol engines directly, instead they should use
24 Detailed information about each NetLabel protocol engine can be found in this
31 protocol built on top of the Generic NETLINK transport mechanism. The exact
38 The purpose of the NetLabel security module API is to provide a protocol
39 independent interface to the underlying NetLabel protocol engines. In addition
40 to protocol independence, the security module API is designed to be completely
Dcipso_ipv4.txt9 The NetLabel CIPSO/IPv4 protocol engine is based on the IETF Commercial IP
17 The CIPSO/IPv4 protocol engine applies the CIPSO IP option to packets by
28 The CIPSO/IPv4 protocol engine validates every CIPSO IP option it finds at the
37 The CIPSO/IPv4 protocol engine contains a mechanism to translate CIPSO security
48 CIPSO/IPv4 protocol engine supports this caching mechanism.
D00-INDEX4 - documentation on the IPv4 CIPSO protocol engine.
6 - IETF draft of the CIPSO protocol, dated 16 July 1992.
/Documentation/ABI/testing/
Dsysfs-class-rc27 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 The enabled wakeup protocol is shown in [] brackets.
73 Writing "+proto" will add a protocol to the list of enabled
75 Writing "-proto" will remove a protocol from the list of enabled
79 Write fails with EINVAL if an invalid protocol combination or
[all …]
Dsysfs-driver-hid-multitouch5 quirks actually in place to handle the device's protocol.
9 the protocol to handle the device.
/Documentation/x86/
Dboot.txt11 Currently, the following versions of the Linux/x86 boot protocol exist.
24 Protocol 2.02: (Kernel 2.4.0-test3-pre3) New command line protocol.
42 Protocol 2.07: (Kernel 2.6.24) Added paravirtualised boot protocol.
53 Protocol 2.10: (Kernel 2.6.31) Added a protocol for relaxed alignment
58 protocol entry point.
97 the 2.02 protocol resolves that problem.
114 For a modern bzImage kernel with boot protocol version >= 2.02, a
170 0206/2 2.00+ version Boot protocol version supported
175 0211/1 2.00+ loadflags Boot protocol option flags
189 0236/2 2.12+ xloadflags Boot protocol option flags
[all …]
/Documentation/networking/
Dsctp.txt7 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
Dphonet.txt1 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:
Dxfrm_proc.txt23 i.e. Either inbound SPI, address, or IPsec protocol at SA is wrong
25 Transformation protocol specific error
61 Transformation protocol specific error
Dx25-iface.txt73 The X.25 packet layer protocol depends on a reliable datalink service.
74 The LAPB protocol provides such reliable service. But this reliability
84 The X.25 packet layer protocol will detect this and reset the virtual
101 driver's LAPB protocol must not confirm reception of the frame
103 This will reliably suppress packet loss. The LAPB protocol will
123 of the LAPB protocol's flow-control service.
Dvxlan.txt4 The VXLAN protocol is a tunnelling protocol that is designed to
9 Vmware and Brocade. The protocol runs over UDP using a single
D00-INDEX8 - info on the 6pack protocol, an alternative to KISS for AX.25
36 - B.A.T.M.A.N routing protocol on top of layer 2 Ethernet Frames.
44 - documentation on CAN protocol family.
128 - User guide to the L2TP tunnel protocol.
162 - The Phonet packet protocol used in Nokia cellular modems.
182 - Guide to the RxRPC protocol.
188 - Notes on the Linux kernel implementation of the SCTP protocol.
216 - UDP-Lite protocol (RFC 3828) introduction.
/Documentation/i2c/
Dsummary4 I2C (pronounce: I squared C) is a protocol developed by Philips. It is a
5 slow two-wire protocol (variable speed, up to 400 kHz), with a high speed
11 SMBus (System Management Bus) is based on the I2C protocol, and is mostly
21 implement all the common SMBus protocol semantics or messages.
47 speak a custom protocol or to emulate some other device.
Dsmbus-protocol4 The following is a summary of the SMBus protocol. It applies to
5 all revisions of the protocol (1.0, 1.1, and 2.0).
6 Certain protocol features which are not supported by
9 Some adapters understand only the SMBus (System Management Bus) protocol,
10 which is a subset from the I2C protocol. Fortunately, many devices use
15 I2C protocol). This makes it possible to use the device driver on both
20 Below is a list of SMBus protocol operations, and the functions executing
21 them. Note that the names used in the SMBus protocol specifications usually
23 single data byte, the functions using SMBus protocol operation names execute
24 a different protocol operation entirely.
[all …]
/Documentation/
Dmailbox.txt8 proprietary and implement non-standard protocol. So even if two
15 ever deal at client's protocol level.
27 or it can never know (the client knows by way of the protocol).
50 * dependent upon the protocol. This is just an example.
92 dc_async->cl.knows_txdone = false; /* depending upon protocol */
102 dc_sync->cl.knows_txdone = false; /* depending upon protocol */
Dpnp.txt98 forwards commands to the proper protocol. This makes writing PnP drivers
110 - use this to register a new PnP protocol
113 - use this function to remove a PnP protocol from the Plug and Play Layer
129 This section contains information for PnP protocol developers.
140 Requirements for a Linux PnP protocol:
141 1.) the protocol must use EISA IDs
142 2.) the protocol must inform the PnP Layer of a device's current configuration
145 The following are PnP protocol related functions:
163 For more information consult the source of a protocol such as
Dhsi.txt6 High Speed Syncronous Interface (HSI) is a fullduplex, low latency protocol,
14 The serial protocol uses two signals, DATA and FLAG as combined data and clock
45 implement a protocol used on the HSI interface. These client drivers can
/Documentation/blockdev/
Dparide.txt19 and the communication protocol provides operations for reading and writing
67 The third component of PARIDE is a set of low-level protocol drivers
102 You can actually select all the protocol modules, and allow the PARIDE
105 For the "brand-name" products listed above, here are the protocol
138 can find, and all protocol types that have been installed, until it finds
142 protocol identification number and, for some devices, the drive's
148 paride: bpck registered as protocol 0
149 paride: epat registered as protocol 1
152 different protocol selections. You should note these numbers as you
169 is the parallel port base address, the 0 is the protocol registration
[all …]
/Documentation/networking/caif/
DLinux-CAIF.txt10 CAIF is a MUX protocol used by ST-Ericsson cellular modems for
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
77 The CAIF protocol can be divided into two parts: Support functions and Protocol
82 and for adding/extracting header and trailers to protocol packets.
160 CAIF Core protocol. The IP Interface and CAIF socket have an instance of
161 'struct cflayer', just like the CAIF Core protocol stack.
/Documentation/misc-devices/mei/
Dmei.txt18 each client has its own protocol. The protocol is message-based with a
36 - Selective network isolation of Ethernet and IP protocol flows based
41 starting with Release 6.0) over HTTP/S or WS-Management protocol over
149 using a protocol called Intel AMT Port Forwarding Protocol(Intel APF protocol).
150 The protocol is used to maintain multiple sessions with Intel AMT from a
153 See the protocol specification in the Intel AMT Software Development Kit(SDK)
/Documentation/input/
Dmulti-touch-protocol.txt12 document describes the multi-touch (MT) protocol which allows kernel
15 The protocol is divided into two types, depending on the capabilities of the
16 hardware. For devices handling anonymous contacts (type A), the protocol
18 devices capable of tracking identifiable contacts (type B), the protocol
28 applications, the MT protocol can be implemented on top of the ST protocol
46 The main difference between the stateless type A protocol and the stateful
47 type B slot protocol lies in the usage of identifiable contacts to reduce
48 the amount of data sent to userspace. The slot protocol requires the use of
217 In the type B protocol, ABS_MT_TOOL_TYPE and ABS_MT_TRACKING_ID are
315 event should be omitted. The protocol currently supports MT_TOOL_FINGER and
[all …]
/Documentation/devicetree/bindings/media/
Dst-rc.txt11 protocol used for receiving remote control signals. rx-mode should
14 protocol used for transmitting remote control signals. tx-mode should
/Documentation/infiniband/
Dcore_locking.txt27 The corresponding functions exported to upper level protocol
59 Because low-level drivers are reentrant, upper level protocol
95 Upper level protocol consumers may not sleep in a callback.
109 An upper level protocol consumer may begin using an IB device as

123456789