linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Janusz Dziedzic <janusz.dziedzic@gmail.com>,
	Sangwoo Moon <swmoon@lanada.kaist.ac.kr>
Cc: Janusz Dziedzic <janusz.dziedzic@tieto.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	ath10k <ath10k@lists.infradead.org>
Subject: Re: [PATCH v2] ath10k: enable VHT for IBSS
Date: Thu, 11 Jun 2015 06:25:44 -0700	[thread overview]
Message-ID: <55798C58.9020600@candelatech.com> (raw)
In-Reply-To: <CAFED-jkdYZaKiEY9RWHTh0+MthbsQri8EhmQZ1j-tjcvzjSVdg@mail.gmail.com>



On 06/10/2015 11:33 PM, Janusz Dziedzic wrote:
> 2015-06-11 8:32 GMT+02:00 Sangwoo Moon <swmoon@lanada.kaist.ac.kr>:
>> Hello,
>>
>> I have successfully installed the latest version of ath10k driver from
>> backports.
>>
>> However, I have some difficulties on configuring wpa_supplicant for IBSS VHT
>> mode.
>> Looked at wpa_supplicant configuration file, but I couldn't found any option
>> related to explicit setting VHT (though I've found disable_vht instead)
>>
>> Sorry for annoying questions, but can you help this out?
>> At least you could let me know your configuration of wpa_supplicant.
>>
> supplicant by default setup wildest BW, no special parameter required
> for IBSS VHT
>
> network = {
>      ssid="ibss"
>      mode=1
>      key_mgmt=NONE
>      frequency=5180
> }
>
> Just use latest version of wpa_supplicant.
> next check you have 80MHz BW
> iw wlan0 info

Make sure you compile supplicant with this option enabled:

CONFIG_IBSS_RSN=y

I think only particular firmware versions are doing to do IBSS as well.

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2015-06-11 13:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10  5:14 [PATCH v2] ath10k: enable VHT for IBSS Janusz Dziedzic
2015-06-10 18:04 ` Sangwoo Moon
2015-06-11  4:28   ` Janusz Dziedzic
2015-06-11  6:32     ` Sangwoo Moon
2015-06-11  6:33       ` Janusz Dziedzic
2015-06-11 13:25         ` Ben Greear [this message]
2015-06-11 14:15 ` Kalle Valo
2015-06-12  5:12   ` Janusz Dziedzic
2015-06-12 13:33     ` Ben Greear
2015-06-15 12:31     ` Kalle Valo
2015-06-16 10:10 ` Kalle Valo

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=55798C58.9020600@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=janusz.dziedzic@gmail.com \
    --cc=janusz.dziedzic@tieto.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=swmoon@lanada.kaist.ac.kr \
    /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;
as well as URLs for NNTP newsgroup(s).