linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: Csaba Kiraly <csaba.kiraly@gmail.com>, linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH] ath9k_htc: advertise support for TDLS
Date: Tue, 19 Aug 2014 10:27:55 +0200	[thread overview]
Message-ID: <53F30A8B.6000202@rempel-privat.de> (raw)
In-Reply-To: <53F309F5.4020101@gmx.net>

[-- Attachment #1: Type: text/plain, Size: 1777 bytes --]

Oppss... wrong email address.

Am 19.08.2014 um 10:25 schrieb Oleksij Rempel:
> Am 18.08.2014 um 01:53 schrieb Csaba Kiraly:
>> Based on a quick test with AR9271, TDLS seems to be working fine.
>>
>> Tests were done with 2 Atheros AR9271 based devices with firmware
>> 1.3 (sha1 8d49f928aa40ac53c729189bff1333cd373a7fb5), associated
>> with a WAP54G access point.
> 
> please, don't use firmware 1.3. Use git source, or you can get
> precompiled version here:
> https://github.com/olerem/ath9k-htc-firmware-blob
> 
>> TDLS worked fine both in WPA2 mode and
>> without encryption. Stations maintained ping flood traffic between
>> each other and towards the AP without significant losses.
>>
>> Not tested with AR7010.
> 
> Seems ok for me. How can i reproduce testing environment?
> 
>> TDLS was enabled in earlier patches the same way for other
>> Atheros drivers:
>> ath9k (fd6562344dea2b8b2a5d644cf971f4e56004500a),
>> and carl9170 (d1f3de71a584a82ee4e84505fce9acccf40215ff).
>>
>> Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
>> ---
>>  drivers/net/wireless/ath/ath9k/htc_drv_init.c | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/net/wireless/ath/ath9k/htc_drv_init.c b/drivers/net/wireless/ath/ath9k/htc_drv_init.c
>> index 8a3bd5f..d779f4f 100644
>> --- a/drivers/net/wireless/ath/ath9k/htc_drv_init.c
>> +++ b/drivers/net/wireless/ath/ath9k/htc_drv_init.c
>> @@ -592,6 +592,8 @@ static void ath9k_set_hw_capab(struct ath9k_htc_priv *priv,
>>  	hw->wiphy->flags |= WIPHY_FLAG_IBSS_RSN |
>>  			    WIPHY_FLAG_HAS_REMAIN_ON_CHANNEL;
>>  
>> +	hw->wiphy->flags |= WIPHY_FLAG_SUPPORTS_TDLS;
>> +
>>  	hw->queues = 4;
>>  	hw->max_listen_interval = 1;
>>  
>>
> 
> 


-- 
Regards,
Oleksij


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

  reply	other threads:[~2014-08-19  8:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-17 23:53 [PATCH] ath9k_htc: advertise support for TDLS Csaba Kiraly
2014-08-19  8:25 ` Oleksij Rempel
2014-08-19  8:27   ` Oleksij Rempel [this message]
2014-08-19 19:00     ` Csaba Kiraly

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=53F30A8B.6000202@rempel-privat.de \
    --to=linux@rempel-privat.de \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=csaba.kiraly@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@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 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).