Changes between Version 16 and Version 17 of 802.11/PacketFlow

Timestamp:

Oct 15, 2014, 8:09:51 PM (10 years ago)

Author:

murphpo

Comment:

--

802.11/PacketFlow

@@ -133 +133 @@
 The lower-level MAC and PHY process a single Tx packet at any given time. While a packet is being transmitted the upper-level MAC prepares the next packet for transmission. Two buffers from the Tx packet buffer RAM are used for this ping-pong approach.
 
-The handshake between the upper and lower level MACs to initiate new packet transmissions is illustrated below. The handshake uses three IPC messages:
+The handshake between the upper and lower level MACs to initiate new packet transmissions is illustrated below. The handshake uses two IPC messages:
  * {{{IPC_MBOX_TX_MPDU_READY(pkt_buf_index)}}}: indication from CPU High that the packet in {{{pkt_buf_index}}} is ready for transmission
- * {{{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.
  * {{{IPC_MBOX_TX_MPDU_DONE(pkt_buf_index)}}}: indication from CPU Low that transmission of the packet in {{{pkt_buf_index}}} is complete.
 
@@ -142 +141 @@
 [[Image(wiki:802.11/files:wlan_tx_ping_pong_msgs.png)]]
 
-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.
+The upper-level MAC framework calls an application-specific callback function upon receipt of the {{{IPC_MBOX_TX_MPDU_DONE}}} message. The MAC application can use this callback to manage internal state, create log entries, update statistics, etc.