From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>, linux-wireless@vger.kernel.org
Cc: Jouni Malinen <j@w1.fi>
Subject: Re: [PATCH] mac80211: Let VHT work on 2.4Ghz
Date: Tue, 23 Feb 2016 15:22:53 +0100 [thread overview]
Message-ID: <1456237373.9910.18.camel@sipsolutions.net> (raw)
In-Reply-To: <56CC6A35.5000900@candelatech.com>
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.
johannes
next prev parent reply other threads:[~2016-02-23 14:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 22:42 [PATCH] mac80211: Let VHT work on 2.4Ghz greearb
2016-02-22 22:48 ` Julian Calaby
2016-02-22 22:55 ` Ben Greear
2016-02-23 10:47 ` Arik Nemtsov
2016-02-23 13:46 ` Ben Greear
2016-02-24 8:40 ` Arik Nemtsov
2016-02-24 13:24 ` Ben Greear
2016-02-24 13:32 ` Arik Nemtsov
2016-02-24 13:37 ` Ben Greear
2016-02-24 14:25 ` Arik Nemtsov
2016-02-23 14:10 ` Johannes Berg
2016-02-23 14:18 ` Ben Greear
2016-02-23 14:22 ` Johannes Berg [this message]
2016-02-23 14:58 ` Ben Greear
2016-02-23 21:08 ` Jouni Malinen
2016-02-23 21:15 ` Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1456237373.9910.18.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.