From: Johannes Berg <johannes@sipsolutions.net>
To: Felix Fietkau <nbd@openwrt.org>
Cc: Krishna Chaitanya <chaitanya.mgit@gmail.com>,
chaitanyatk@posedge.com, linux-wireless@vger.kernel.org,
maheshp@posedge.com
Subject: Re: [RFC] mac80211: Add support for Tx-AMSDU viz debugfs.
Date: Thu, 07 Feb 2013 15:17:33 +0100 [thread overview]
Message-ID: <1360246653.8038.9.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <5113B42A.4020708@openwrt.org>
On Thu, 2013-02-07 at 15:03 +0100, Felix Fietkau wrote:
> > But the problem is every time we have to test the Rx-AMSDU
> > which is mandatory for WFA 802.11n cert, we need to procure a adapter
> > which supports it, which is difficult. Thats the scenario we have faced
> > which lead us to work on this.With this feature in place we can use
> > any opensource adapter and driver for that purpose.
> >
> > Again, Its a trade off between stability and usability :-)
> How about injecting A-MSDU packets via cooked monitor mode or nl80211
> frame tx and thus shifting the debug-only code into userspace?
nl80211 won't work -- no support for data frames (and I'd rather not add
it), but monitor mode (why cooked?) seems fine.
johannes
next prev parent reply other threads:[~2013-02-07 14:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 8:01 [RFC] mac80211: Add support for Tx-AMSDU viz debugfs chaitanyatk
2013-02-07 8:20 ` Johannes Berg
2013-02-07 9:19 ` Krishna Chaitanya
2013-02-07 9:23 ` Johannes Berg
2013-02-07 9:30 ` Krishna Chaitanya
2013-02-07 14:03 ` Felix Fietkau
2013-02-07 14:17 ` Johannes Berg [this message]
2013-02-07 14:57 ` Krishna Chaitanya
2013-02-07 15:18 ` Felix Fietkau
2013-02-07 15:27 ` Johannes Berg
2013-02-11 7:54 ` Krishna Chaitanya
2013-02-11 8:46 ` Johannes Berg
2013-02-11 9:28 ` Krishna Chaitanya
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=1360246653.8038.9.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chaitanya.mgit@gmail.com \
--cc=chaitanyatk@posedge.com \
--cc=linux-wireless@vger.kernel.org \
--cc=maheshp@posedge.com \
--cc=nbd@openwrt.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.