From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: Sujith Manoharan <c_manoha@qualcomm.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
<linux-wireless@vger.kernel.org>,
Rodriguez Luis <rodrigue@qca.qualcomm.com>,
<ath9k-devel@lists.ath9k.org>,
Antonio Quartulli <ordex@autistici.org>
Subject: Re: [RFC 1/2] ath9k_htc: Advertize allowed vif combinations
Date: Fri, 28 Sep 2012 10:27:58 +0530 [thread overview]
Message-ID: <50652E56.10303@qca.qualcomm.com> (raw)
In-Reply-To: <20581.2614.43943.601901@gargle.gargle.HOWL>
Hi Sujith,
On Friday 28 September 2012 07:53 AM, Sujith Manoharan wrote:
> Mohammed Shafi Shajakhan wrote:
>> From: Antonio Quartulli <ordex@autistici.org>
>>
>> Advertize allowed VIFs combinations to the cfg80211 sublayer.
>> Other than that, practical tests shown that ath9k_htc devices allow an
>> IBSS VIF to coexist with VIF set up on other modes, so advertize
>> that to. We can also further add p2p/mesh mode to be advertized
>> in the combinations allowed.
>
> I don't think IBSS can co-exist with other op-modes.
>
oh yeah, you are saying that we will have some issues with IBSS
coexistence with other modes because of TSF sync.
Antonio seems to be testing this sometime back and came up with the
following observation :
"ath9k_htc is running since some hours with AP+IBSS without any
problems.What I think that the maintainer was referring to is a general
problem of IBSS+AP: in most devices, TFS is unique among VIFs, therefore
TSF jumps introduced by IBSS can be reflected in a bad way on the AP VIF".
please let us know if you have further thoughts about this.
I will just look into the code if we have some more limitations.
thanks for your review!
--
thanks,
shafi
next prev parent reply other threads:[~2012-09-28 4:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 15:52 [RFC 1/2] ath9k_htc: Advertize allowed vif combinations Mohammed Shafi Shajakhan
2012-09-27 15:52 ` [RFC 2/2] ath9k_htc: Remove interface combination specific checks Mohammed Shafi Shajakhan
2012-09-27 15:53 ` [RFC 1/2] ath9k_htc: Advertize allowed vif combinations Mohammed Shafi Shajakhan
2012-09-27 16:02 ` Antonio Quartulli
2012-09-28 2:23 ` Sujith Manoharan
2012-09-28 4:57 ` Mohammed Shafi Shajakhan [this message]
2012-09-28 10:42 ` Sujith Manoharan
2012-09-29 9:31 ` Antonio Quartulli
2012-09-29 14:22 ` Adrian Chadd
2012-10-08 15:50 ` Mohammed Shafi
2012-10-10 0:10 ` Antonio Quartulli
2012-10-10 15:19 ` Mohammed Shafi
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=50652E56.10303@qca.qualcomm.com \
--to=mohammed@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=c_manoha@qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=ordex@autistici.org \
--cc=rodrigue@qca.qualcomm.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;
as well as URLs for NNTP newsgroup(s).