From: Antonio Quartulli <ordex@autistici.org>
To: Mohammed Shafi <shafi.wireless@gmail.com>
Cc: Sujith Manoharan <c_manoha@qualcomm.com>,
Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
Rodriguez Luis <rodrigue@qca.qualcomm.com>,
ath9k-devel@lists.ath9k.org
Subject: Re: [RFC 1/2] ath9k_htc: Advertize allowed vif combinations
Date: Wed, 10 Oct 2012 02:10:24 +0200 [thread overview]
Message-ID: <20121010001024.GE22517@ritirata.org> (raw)
In-Reply-To: <CAD2nsn20s3L8b8DT53JYAN-t4q5GpxUVzSCncTt1LQO3w=wsYw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
On Mon, Oct 08, 2012 at 09:20:38PM +0530, Mohammed Shafi wrote:
> On Sat, Sep 29, 2012 at 3:01 PM, Antonio Quartulli <ordex@autistici.org> wrote:
> > On Fri, Sep 28, 2012 at 04:12:40 +0530, Sujith Manoharan wrote:
> >> Mohammed Shafi Shajakhan wrote:
> >> > oh yeah, you are saying that we will have some issues with IBSS
> >> > coexistence with other modes because of TSF sync.
> >>
> >> Yes, this is a problem.
> >
> > Is there anyway to overcome this problem? Can we bind the single TSF to multiple
> > virtualTSF? or must the device somehow support us?
>
> Antonio, agained i checked with the ath9k_htc maintainer, he said the
> IBSS coexistence is not
> possible. So i would go with my current patch. Please do feel free to
> enhance. Currently
> i am working in some other project, not sure i would be able to take this up.
Hi Mohammed,
thank you for having taken care of this. Is it possible to have more details
about this "impossibility"? I still have to understand, because on one side we
all agreed on the fact that IBSS+AP coexistence will create problems on the STA
(connected to the AP) because of the TSF jumps, but this would still "work". On
the other side the maintainer is claiming this would not work at all :-) At this
point, I'd like to clearly understand "why" he is claiming so: is it for the
same reason explained above (TSF jumps) or is there something else?
Cheers,
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-10-10 0:10 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
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 [this message]
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=20121010001024.GE22517@ritirata.org \
--to=ordex@autistici.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=c_manoha@qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mohammed@qca.qualcomm.com \
--cc=rodrigue@qca.qualcomm.com \
--cc=shafi.wireless@gmail.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).