From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "michal.kazior@tieto.com" <michal.kazior@tieto.com>
Cc: Ben Greear <greearb@candelatech.com>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: QCA99XX with MU-MIMO and beamforming?
Date: Tue, 26 Apr 2016 09:44:03 +0000 [thread overview]
Message-ID: <878u00zov2.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQke1auNL1-oPN-N9=e9K5vit0w2iJSS9KuXEifR7hqm6Q@mail.gmail.com> (Michal Kazior's message of "Tue, 26 Apr 2016 08:16:06 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> On 25 April 2016 at 22:31, Ben Greear <greearb@candelatech.com> wrote:
>> Has anyone tried this? Looks like hostapd has the ability to set the
>> feature flags, but I am not sure if it is really working in ath10k?
>
> Yes, it works. You need a few vht_capabs. I have mine like this:
>
> > vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][BF-ANTENNA-4][MAX-MPDU-11454][RX-STBC-1][MAX-A-MPDU-LEN-EXP7]
>
> The SU-, MU- and BF- are the required part only I think.
If/when you have time, could you please mention something about this in
the wiki:
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/configuration#hostapd
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-04-26 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 20:31 QCA99XX with MU-MIMO and beamforming? Ben Greear
2016-04-26 6:16 ` Michal Kazior
2016-04-26 9:44 ` Valo, Kalle [this message]
2016-04-26 14:35 ` Ben Greear
2016-04-27 6:37 ` Michal Kazior
2016-05-02 17:59 ` Ben Greear
2016-05-04 8:32 ` Michal Kazior
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=878u00zov2.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=michal.kazior@tieto.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox