BTnut System Software Data Structures

Here are the data structures with brief descriptions:
/home/beutel/eclipse/btnut/btnode/include/bt/bt_hci_api.hRepresents one entity of a running stack (more than one possible) Keeps all data for one stack, like devices, buffers, states, ... This is the main struct your program should have
__iobufStores the current status of a stream
_ACEDCBACE device control block structure
_AHDLCDCBAsynchronous HDLC device information structure
_ARPENTRYARP entry structure
_AT45_DEVTABKnown device type entry
_AT45DB_DCBActive device entry
_AUTHINFOHTTP authorization information structure
_bt_acl_com_buffer_entry
_bt_acl_com_service
_bt_acl_com_stack
_CANFRAMECAN frame structure
_CANINFOCAN controller information structure
_CGIFUNCTIONRegistered CGI function
_cm_neighborNeighbor Parameters
_cm_stackConnection manager stack
_CONFNETNetwork configuration structure
_CONFOSOperating system configuration structure
_dirdescInternally used directory information structure
_fifo_queue_tRepresentation of a FIFO queue
_HEAPNODEHeap memory node information structure
_IFSTREAMStream interface information structure
_log_msg_tail_sDefinition of the log message trailer
_mhop_cl_pkt_hdrDefinition of the multi-hop control header
_mhop_cl_stack_sConnection-less multi-hop stack
_MMCDCBPrivate data of NPL card interface
_MMCFCBLocal multimedia card mount information
_MMCIFCLow level access information structure
_mutexRecursive mutex
_NBDATAData part of a network buffer structure
_NETBUFNetwork buffer structure
_NICINFONetwork interface controller information structure
_NUTDEVICEDevice structure
_NUTFILEFile structure
_NUTRTCRTC device structure
_NUTTHREADINFOThread information structure
_NUTTIMERINFOTimer information structure
_NUTVIRTUALDEVICEVirtual device structure
_PHATFILEPHAT file descriptor structure
_PHATSECTBUFSector buffer structure
_PHATVOLVolume info structure
_PNUTFILEPNUT file descriptor structure
_PPPDCBPPP interface structure
_REQUESTHTTP request information structure
_RINGBUFCharacter device ring buffer structure
_ROMENTRYMikro-ROM directory entry structure
_ROMFILEMikro-ROM file information structure
_RTENTRYRoute entry structure
_sync_nbRepresents a neighbour BTnode Make use of the typedef'd type sync_neighbour.
A linked list is formed out of these elements in order to store the time of the last receiveing/sending event with the corresponding BTnode. The list is always ordered. The BTnode of the latest communication is at the beginning of the list, the BTnode of the oldest communication is at the end. Maximal SYNC_MAX_NEIGHBOURS neighbours are allowed. If already SYNC_MAX_NEIGHBOURS are stored in the list, the oldest (last) entry will be removed
_t_traceitemItem in the trace buffer
_TCPPSEUDOHDRTCP pseudo header structure
_TERMDCBTerminal device control block structure
_tmStructure to store a date/time value
_tvRepresents unix time in seconds and microseconds
_UARTDCBUART device control block structure
_UNIXDCBUNIX devices low level information structure
_USARTDCBUSART device low level information structure
_xbank_prog_info_sProgram information struct
arphdrARP packet header structure
bt_acl_pkt_buf_sACL Packet Buffer Definition
bt_hci_cmd_response
bt_hci_connection
bt_hci_inquiry_result
bt_hci_local_version_result
bt_hci_pkt_acl
bt_hci_pkt_cmd
bt_hci_pkt_evt
bt_hci_pkt_sco
bt_hci_uart
bt_l2cap_acl_buffer_entryBuffer entry for internal acl packet buffering
bt_l2cap_acl_pktRepresents one l2cap packet including the acl header
bt_l2cap_bb_connection
bt_l2cap_channelThis struct represents one l2cap channel
bt_l2cap_channel_info_dataThis struct contains some internal information to process the packets. A pointer to this information is added at the end of a l2cap data packet
bt_l2cap_pkt_buffer_entryBuffer entry for internal l2cap packet buffering
bt_l2cap_serviceThis struct represents one service
bt_l2cap_signalThis struct contains the header fields of a l2cap signaling packet
bt_l2cap_signal_bufferBuffer entry for internal l2cap signal buffering
bt_l2cap_stackRepresents one entity of the l2cap layer itself
bt_semaphoreRepresents a bt_semaphore, a number of ressources that can be shared by many threads
btstackRepresents one entity of a running stack (more possible) Keeps all data for one stack, like devices, buffers, states, ..
ccc_packet_st
con_mgr_stack_sDefinition of the connection manager stack
DEVDCBDevice driver's private data structure
direntDirectory entry structure
dyn_cfgDynamic configuration structure
ether_arpEthernet ARP protocol structure
ether_headerEthernet protocol header
FTPSESSIONFTP session information structure
icmpICMP protocol header structure
ifcanCAN interface structure
ifnetNetwork interface structure
IOCTL_ARG2General structure for two arguments
IOCTL_ARG3General structure for three arguments
mac_interface_st
mhop_cl_fwt_entry_sForwarding table entry
NICINFO
PNUT_DIRENTRYDirectory entry structure
PNUT_FINDRESULTDirectory search result information structure
PNUT_NODENode structure
statFile status structure
syncboundsRepresents a pair of bounds
tcp_socketTCP socket information structure
tcphdrTCP protocol header structure
udp_socketUDP socket information structure
udphdrUDP protocol header structure

Generated on Tue Jan 23 21:12:31 2007 for BTnut System Software by doxygen 1.4.7