Changes between Version 15 and Version 16 of 802.11/PacketFlow
- Timestamp:
- Oct 14, 2014, 4:32:59 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
802.11/PacketFlow
v15 v16 135 135 The handshake between the upper and lower level MACs to initiate new packet transmissions is illustrated below. The handshake uses three IPC messages: 136 136 * {{{IPC_MBOX_TX_MPDU_READY(pkt_buf_index)}}}: indication from CPU High that the packet in {{{pkt_buf_index}}} is ready for transmission 137 * {{{IPC_MBOX_TX_MPDU_ACCEPT(pkt_buf_index }}}: indication from CPU Low that the packet in {{{pkt_buf_index}}} is currently being transmitted by the lower-level MAC and PHY. This message always follows the corresponding {{{IPC_MBOX_TX_MPDU_READY}}}137 * {{{IPC_MBOX_TX_MPDU_ACCEPT(pkt_buf_index)}}}: indication from CPU Low that the packet in {{{pkt_buf_index}}} is currently being transmitted by the lower-level MAC and PHY. This message always follows the corresponding {{{IPC_MBOX_TX_MPDU_READY}}} and precedes the corresponding {{{IPC_MBOX_TX_MPDU_DONE}}}. The upper-level MAC may safely ignore this message if desired. 138 138 * {{{IPC_MBOX_TX_MPDU_DONE(pkt_buf_index)}}}: indication from CPU Low that transmission of the packet in {{{pkt_buf_index}}} is complete. 139 139 … … 141 141 142 142 [[Image(wiki:802.11/files:wlan_tx_ping_pong_msgs.png)]] 143 144 The upper-level MAC framework calls application-specific callback functions upon receipt of {{{IPC_MBOX_TX_MPDU_ACCEPT}}} and {{{IPC_MBOX_TX_MPDU_DONE}}} messages. The MAC application can use these callbacks to manage internal state, create log entries, update statistics, etc.