01.06.2013 Views

IPC@CHIP Documentation - SC12 @CHIP-RTOS V1.10

IPC@CHIP Documentation - SC12 @CHIP-RTOS V1.10

IPC@CHIP Documentation - SC12 @CHIP-RTOS V1.10

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>IPC<strong>@CHIP</strong></strong> <strong>Documentation</strong> Index<br />

Data Structures<br />

Data Structures used in TCP/IP API - <strong>SC12</strong> <strong>@CHIP</strong>-<strong>RTOS</strong> <strong>V1.10</strong><br />

Here are the BSD structures and other data types used by the TCP/IP API.<br />

All constants and data structures are defined in the TCPIPAPI.H header file.<br />

Notes:<br />

1. Byte alignment is required within all data structures used within the API.<br />

2. The phrase "network byte order" means big endian (like Motorola machines, unlike Intel).<br />

Contents :<br />

● typedef_ArpHeader<br />

● typedef_ArpRouteCacheEntry<br />

● typedef_ArpUserCallbackInfo<br />

● typedef_atEntry<br />

● typedef_DevUserBuffer<br />

● typedef_DevUserBufferHandle<br />

● typedef_DevUserDriver<br />

● typedef_DevUserIfaceHandle<br />

● typedef_DevUserLinkLayer<br />

● typedef_GetSocketOption<br />

● typedef_IcmpMib<br />

● typedef_Iface_Entry<br />

● typedef_IfMib<br />

● struct_in_addr<br />

● typedef_IpMib<br />

● struct_IpUserCallbackInfo<br />

● typedef_Packet_Count<br />

● typedef_PasCallBack<br />

● typedef_Ping<br />

● typedef_PPPClient_Init<br />

● typedef_PPPDial<br />

● typedef_PPP_IPCfg_Data<br />

● typedef_PPP_ModemHangup<br />

● typedef_PPP_Option<br />

● struct_recv_params<br />

● typedef_Route_Entry<br />

● struct_send_params<br />

● typedef_SetSocketOption<br />

● struct_sockaddr<br />

● struct_sockaddr_in<br />

● typedef_SocketInfo<br />

● typedef_TcpMib<br />

● typedef_UdpMib<br />

● typedef_UserEthDhcp_Entry<br />

Page 160 / 400

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!