Comment # 32
on bug 9586
from Emburey
(In reply to comment #28)
> (In reply to comment #20)
> > field 'flagsN'
> >
> > (first 23 bits) 0/1 0/1 0/1 0/1 0/1 0/1 0/1 0/1 0/1
> > | | | | | | | | | |
> > | | | | | | | | | |- 802.11ac 20MHz
> > lower
> > | | | | | | | | |------ 802.11ac 20MHz
> > upper
> > | | | | | | | |----------- 802.11ac 40MHz
> > | | | | | | |---------------- 802.11ac HALF
> > GI
> > | | | | | |--------------------- 802.11ac FULL
> > GI
> > | | | | |-------------------------- 802.11ac AMPDU
> > | | | |------------------------------- 802.11ac AMSDU
> > | | |------------------------------------ -nil-
> > | |----------------------------------------- 802.11ac
> > future use
> > |----------------------------------------------------- -nil-
>
> I presume you mean "802.11n", given that 1) the field has a big capital "N"
> at the end of its name and 2) those are all features in 802.11n.
Yes. The 'FlagsN' is specific for 802.11n, and would not come for the legacy
header.
You are receiving this mail because:
- You are watching all bug changes.