Changes between Version 6 and Version 7 of 802.11/wlan_exp/Porting_v1.5

Timestamp:

Apr 19, 2016, 11:11:13 AM (8 years ago)

Author:

murphpo

Comment:

--

802.11/wlan_exp/Porting_v1.5

@@ -119 +119 @@
 == Tx/Rx Entry Changes ==
 
-'''{{{phy_mode}}} Field'''[[BR]]
+{{{#!th
+v1.4
+}}}
+{{{#!th
+v1.5
+}}}
+{{{#!th
+Notes
+}}}
+{{{#!tr valign=top
+{{{#!td align=center
+ n/a
+}}}
+{{{#!td align=center
+{{{phy_mode}}}
+}}}
+{{{#!td
 Starting in v1.5 the reference design supports both non-HT (11a) and HTMF (11n) waveforms. The Tx and Rx PHY can switch between PHY modes per-packet. The Tx/Rx log entries have a {{{phy_mode}}} field which encodes which mode was used for a given Tx/Rx event. The {{{NONHT}}} PHY mode (11a) has value {{{1}}}; the {{{HTMF}}} PHY mode (11n) has value {{{2}}}.
-
-'''{{{mcs}}} Field'''[[BR]]
-Previous releases defined a {{{rate}}} field in Tx and Rx entries. The {{{rate}}} value was an index into the array of 8 supported 11a rates. Starting in v1.5 the {{{rate}}} field is replaced by {{{mcs}}} and always records the MCS index of the Tx/Rx waveform. The {{{mcs}}} value must be combined with the {{{phy_mode}}} value to know what PHY rate and mode were used for a given Tx/Rx event.
-
-'''{{{pkt_type}}} Field'''[[BR]]
+}}}
+}}}
+{{{#!tr valign=top
+{{{#!td align=center
+{{{rate}}}
+}}}
+{{{#!td align=center
+{{{mcs}}}
+}}}
+{{{#!td 
+Previous releases defined a {{{rate}}} field in Tx and Rx entries. The {{{rate}}} value was an index into the array of 8 supported 11a rates. Starting in v1.5 the {{{rate}}} field is replaced by {{{mcs}}} and always records the MCS index of the Tx/Rx waveform. The {{{mcs}}} value must be combined with the {{{phy_mode}}} value to know what PHY rate and mode were used for a given Tx/Rx event.}}}
+}}}
+}}}
+{{{#!tr valign=top
+{{{#!td align=center
+{{{pkt_type}}}
+}}}
+{{{#!td align=center
+{{{pkt_type}}}
+}}}
+{{{#!td 
 Previous releases defined a {{{pkt_type}}} field in Tx and Rx log entries. This field had values like {{{LTG}}} and {{{ACK}}}. The mapping of 802.11 packet types to {{{pkt_type}}} values was arbitrary, implemented in the reference C code. Starting in v1.5 the {{{pkt_type}}} field is a copy of the 1-byte {{{frame_control1}}} field from the packet's 802.11 header. This field encodes the type (Data, Management or Control) and sub-type (i.e. QoS Data, Protected Data; Probe Request, Beacon; RTS, ACK). The reference code does not modify the type/sub-type values recorded in the {{{pkt_type}}} log entries.
-
-'''{{{timestamp_frac}}} Field'''[[BR]]
+}}}
+}}}
+{{{#!tr valign=top
+{{{#!td align=center
+{{{timestamp_frac}}}
+}}}
+{{{#!td align=center
+{{{timestamp_frac}}}
+}}}
+{{{#!td 
 Tx/Rx entries have always had a {{{timestamp}}} field which records the MAC Time in microseconds of each Tx/Rx event. Starting in v1.5 the MAC/PHY hardware also records a "fractional" timestamp for Tx/Rx events. By combining the {{{timestamp}}} and {{{timestamp_frac}}} values the timing of a Tx/Rx event can be resolved with sample-period accuracy.
 
 The fractional timestamp value records the value of the counter in the {{{wlan_mac_time_hw}}} core which defines the microsecond intervals for the MAC and System Times. This counter counts from 0 to 159 at 160MHz (i.e. 160 cycles @ 160MHz = 1 µsec). Thus the {{{timestamp_frac}}} field will have values in {{{[0, 1, ... 159]}}}. To translate this value into a fraction of a microsecond, divide the {{{timestamp_frac}}} value by 160.
+}}}
+}}}
 
-'''Renamed {{{TX}}} entry type to {{{TX_HIGH}}}'''[[BR]]
-The {{{TX_HIGH}}} entry type (named {{{TX}}} in previous releases) records each packet which passes through a queue in the upper MAC framework. Each {{{TX_HIGH}}} entry will have 0 or more {{{TX_LOW}}} entries, depending on how the lower MAC handles the transmission event.
-