On 02/23/2016 06:22 AM, Johannes Berg wrote:
On Tue, 2016-02-23 at 06:18 -0800, Ben Greear wrote:
[root@ben-ota2 lanforge]# iw phy wiphy0 info
Wiphy wiphy0
Band 1:
[...]
VHT Capabilities (0x338001b2):
Max MPDU length: 11454
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
TX STBC
RX antenna pattern consistency
TX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: MCS 0-9
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: MCS 0-9
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
Frequencies:
* 2412 MHz [1] (30.0 dBm)
[...]
Oops. Well, the driver isn't supposed to do that, this is certainly
non-spec behaviour.
Is there any harm though? There is at least one other AP manufacturer
that really wants to test this feature, so I guess there will be products
on the market soon enough that support VHT in 2.4Ghz band.
Some day soon-ish, we'll benchmark this in an isolation chamber & over-the-air to see
how it actually performs.
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
