Lines Matching +full:packet +full:- +full:oriented

1 .\" Copyright (c) 2001-2002 Maksim Yevmenkin <m_evmenkin@yahoo.com>
45 L2CAP provides connection-oriented and connectionless data services to upper
52 .Bl -enum -offset indent
56 delivery of data packets, although there might be individual packet corruption
60 The Baseband always provides the impression of full-duplex communication
62 This does not imply that all L2CAP communications are bi-directional.
78 Each channel is bound to a single protocol in a many-to-one fashion.
82 Each L2CAP packet received on a channel is directed to
85 Each one of the end-points of an L2CAP channel is referred to by a channel
88 channel end-point on the device.
92 illegal identifier and must never be used as a destination end-point.
94 CID 0x0002 is reserved for group-oriented channel.
106 .Bl -tag -width foo
116 In this state, the CID represents a local end-point and an L2CAP Connect
120 In this state, the remote end-point exists and an L2CAP Connect Request has
186 packets may be reassembled into a single larger L2CAP packet.
198 .Bl -dash -offset indent
211 .Bl -tag -width ".Va hci"
244 .Bl -tag -width foo
249 device's 48-bit address (BD_ADDR).
263 are the remote device's 48-bit address, Identifier sent in the request, local
272 incoming receivable MTU (InMTU), new outgoing flow spec-ification, and flush
278 the request has been sent to, the outgoing MTU size (maximum packet that can
298 is zero if an L2CAP Disconnect Response is received, otherwise a non-zero value
309 .Bd -literal -offset indent
310 /* L2CA data packet header */
327 .Bf -emphasis
332 .Bf -emphasis
340 .Bf -emphasis
348 .Bf -emphasis
358 .Bf -emphasis
382 .Bl -tag -width foo