Lines Matching refs:and

18 communication between Modem and host. The host processes can open virtual AT
19 channels, initiate GPRS Data connections, Video channels and Utility Channels.
20 The Utility Channels are general purpose pipes between modem and host.
23 and host. Currently, UART and Loopback are available for Linux.
31 * CAIF Socket Layer and GPRS IP Interface.
69 The architecture is inspired by the design patterns "Protocol Layer" and
82 	CAIF payload with receive and transmit functions.
83       -	Clients must call configuration function to add and connect the
91 The CAIF protocol can be divided into two parts: Support functions and Protocol
95 	CAIF Packet has functions for creating, destroying and adding content
96 	and for adding/extracting header and trailers to protocol packets.
101 	Stack and provides a Client interface for adding Link-Layer and
104       - CFCTRL CAIF Control layer. Encodes and Decodes control messages
105 	such as enumeration and channel setup. Also matches request and
109 	control and remote shutdown requests.
118 	physical bearers and multiple channels such as VEI, Datagram, etc.
119 	The MUX keeps track of the existing CAIF Channels and
120 	Physical Instances and selects the appropriate instance based
121 	on Channel-Id and Physical-ID.
124 	and frame checksum.
176 CAIF Socket and IP interface
179 The IP interface and CAIF socket API are implemented on top of the
180 CAIF Core protocol. The IP Interface and CAIF socket have an instance of
182 Net device and Socket implement the 'receive()' function defined by
183 'struct cflayer', just like the rest of the CAIF stack. In this way, transmit and
190 Payload handling and registration is done using standard Linux mechanisms.