Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Thomas Wagner <thomas.wagner@hs-rm.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH v2] ath9k: Fix mesh related rx filtering issue for older chips
Date: Fri, 14 Sep 2012 20:54:38 +0200	[thread overview]
Message-ID: <1518263.XlGm7EvTdD@buri> (raw)
In-Reply-To: <50534AE3.3060107@openwrt.org>

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


Tom

  reply	other threads:[~2012-09-14 18:54 UTC|newest]

Thread overview: 5+ 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 15:18 ` Felix Fietkau
2012-09-14 18:54   ` Thomas Wagner [this message]
2012-09-17  5:17     ` Mohammed Shafi Shajakhan
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=1518263.XlGm7EvTdD@buri \
    --to=thomas.wagner@hs-rm.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox