From: Johannes Berg <johannes@sipsolutions.net>
To: Helmut Schaa <helmut.schaa@googlemail.com>,
linux-wireless@vger.kernel.org
Cc: nbd@openwrt.org
Subject: Re: [PATCHv2] mac80211: Copy tx'ed beacons to monitor mode
Date: Fri, 18 Sep 2015 11:07:57 +0200 [thread overview]
Message-ID: <1442567277.2168.7.camel@sipsolutions.net> (raw)
In-Reply-To: <1441784792-8847-1-git-send-email-helmut.schaa@googlemail.com> (sfid-20150909_094823_520248_88378E64)
On Wed, 2015-09-09 at 09:46 +0200, Helmut Schaa wrote:
> When debugging wireless powersave issues on the AP side it's quite
> helpful
> to see our own beacons that are transmitted by the hardware/driver.
> However,
> this is not that easy since beacons don't pass through the regular TX
> queues.
>
> Preferably drivers would call ieee80211_tx_status also for tx'ed
> beacons
> but that's not always possible. Hence, just send a copy of each
> beacon
> generated by ieee80211_beacon_get_tim to monitor devices when they
> are
> getting fetched by the driver.
>
> Also add a HW flag IEEE80211_HW_BEACON_TX_STATUS that can be used by
> drivers to indicate that they report TX status for beacons.
>
Applied.
johannes
prev parent reply other threads:[~2015-09-18 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 11:23 [PATCH 1/2] mac80211: Split sending tx'ed frames to monitor interfaces into its own function Helmut Schaa
2015-09-02 11:23 ` [PATCH 2/2] mac80211: Copy tx'ed beacons to monitor mode Helmut Schaa
2015-09-08 16:42 ` Johannes Berg
2015-09-09 7:46 ` [PATCHv2] " Helmut Schaa
2015-09-18 9:07 ` Johannes Berg [this message]
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=1442567277.2168.7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--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.