Lines Matching refs:and

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