From: Felix Fietkau <nbd@openwrt.org>
To: Helmut Schaa <helmut.schaa@googlemail.com>,
linux-wireless@vger.kernel.org
Cc: johannes@sipsolutions.net
Subject: Re: [RFC 2/2] mac80211: Copy tx'ed beacons to monitor mode
Date: Tue, 1 Sep 2015 16:04:21 +0200 [thread overview]
Message-ID: <55E5B065.8050107@openwrt.org> (raw)
In-Reply-To: <1441102364-32516-3-git-send-email-helmut.schaa@googlemail.com>
On 2015-09-01 12:12, 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.
How about also adding a hw flag to allow drivers to indicate that they
submit tx status for beacons.
- Felix
next prev parent reply other threads:[~2015-09-01 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 10:12 [RFC 0/2] Send own beacons to monitor interfaces Helmut Schaa
2015-09-01 10:12 ` [RFC 1/2] mac80211: Split sending tx'ed frames to monitor interfaces into its own function Helmut Schaa
2015-09-01 10:12 ` [RFC 2/2] mac80211: Copy tx'ed beacons to monitor mode Helmut Schaa
2015-09-01 14:04 ` Felix Fietkau [this message]
2015-09-01 14:30 ` Helmut Schaa
2015-09-01 15:53 ` Johannes Berg
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=55E5B065.8050107@openwrt.org \
--to=nbd@openwrt.org \
--cc=helmut.schaa@googlemail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).