From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH v2] ath9k: Fix mesh related rx filtering issue for older chips
Date: Mon, 17 Sep 2012 20:42:30 +0530 [thread overview]
Message-ID: <50573DDE.2060502@qca.qualcomm.com> (raw)
In-Reply-To: <5056B274.5050901@qca.qualcomm.com>
Hi Tom,
On Monday 17 September 2012 10:47 AM, Mohammed Shafi Shajakhan wrote:
> Hi Tom,
>
> + linux-wireless
>
> On Saturday 15 September 2012 12:24 AM, Thomas Wagner wrote:
>> Hi,
>>
>>> I'm really not sure about this being tied to sc->nvifs.
>>> If it's mesh related, how about just adding a check for the number of
>>> mesh interfaces [...]
>> No, it is not mesh related!
>> Several frames where filtered out.
>> I discovered this on trying to set up a mesh.
>> But the where filtered frames beyond the mesh: e.g. a beacon of
>> 802.11b Sitecom Router
>>
>> @Felix: Pleas forward this mail to:
>> linux-wireless at vger.kernel.org
>> ath9k-devel at venema.h4ckr.net
>>
>>
>
> thanks for the clarification.
>
>
will send a v3 soon changing the subject and commit log mentioning
generically that the older hardware chipsets seem to filter some
necessary wifi frames ?. thanks!
--
thanks,
shafi
WARNING: multiple messages have this Message-ID (diff)
From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: Thomas Wagner <thomas.wagner@hs-rm.de>
Cc: Felix Fietkau <nbd@openwrt.org>,
Rodriguez Luis <rodrigue@qca.qualcomm.com>,
"John W. Linville" <linville@tuxdriver.com>,
<ath9k-devel@venema.h4ckr.net>,
Javier Cardona <javier@cozybit.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] ath9k: Fix mesh related rx filtering issue for older chips
Date: Mon, 17 Sep 2012 20:42:30 +0530 [thread overview]
Message-ID: <50573DDE.2060502@qca.qualcomm.com> (raw)
In-Reply-To: <5056B274.5050901@qca.qualcomm.com>
Hi Tom,
On Monday 17 September 2012 10:47 AM, Mohammed Shafi Shajakhan wrote:
> Hi Tom,
>
> + linux-wireless
>
> On Saturday 15 September 2012 12:24 AM, Thomas Wagner wrote:
>> Hi,
>>
>>> I'm really not sure about this being tied to sc->nvifs.
>>> If it's mesh related, how about just adding a check for the number of
>>> mesh interfaces [...]
>> No, it is not mesh related!
>> Several frames where filtered out.
>> I discovered this on trying to set up a mesh.
>> But the where filtered frames beyond the mesh: e.g. a beacon of
>> 802.11b Sitecom Router
>>
>> @Felix: Pleas forward this mail to:
>> linux-wireless@vger.kernel.org
>> ath9k-devel@venema.h4ckr.net
>>
>>
>
> thanks for the clarification.
>
>
will send a v3 soon changing the subject and commit log mentioning
generically that the older hardware chipsets seem to filter some
necessary wifi frames ?. thanks!
--
thanks,
shafi
next prev parent reply other threads:[~2012-09-17 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 14:49 [ath9k-devel] [PATCH v2] ath9k: Fix mesh related rx filtering issue for older chips Mohammed Shafi Shajakhan
2012-09-14 14:49 ` Mohammed Shafi Shajakhan
2012-09-14 15:18 ` [ath9k-devel] " Felix Fietkau
2012-09-14 15:18 ` Felix Fietkau
2012-09-14 18:54 ` [ath9k-devel] " Thomas Wagner
2012-09-17 5:17 ` Mohammed Shafi Shajakhan
2012-09-17 5:17 ` Mohammed Shafi Shajakhan
2012-09-17 15:12 ` Mohammed Shafi Shajakhan [this message]
2012-09-17 15:12 ` Mohammed Shafi Shajakhan
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=50573DDE.2060502@qca.qualcomm.com \
--to=mohammed@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.