From: Elliot Schwartz <elliot@devicescape.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: David Kimdon <david.kimdon@devicescape.com>,
netdev@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Jiri Benc <jbenc@suse.cz>
Subject: Re: [patch 5/5] d80211: add ioctl to stop data frame tx
Date: Mon, 28 Aug 2006 11:29:24 -0700 [thread overview]
Message-ID: <uwt8sww6z.fsf@devicescape.com> (raw)
In-Reply-To: <1156317906.3629.18.camel@ux156> (Johannes Berg's message of "Wed, 23 Aug 2006 09:25:06 +0200")
Hi Johannes,
Johannes Berg <johannes@sipsolutions.net> writes:
> On Tue, 2006-08-22 at 10:34 -0700, David Kimdon wrote:
> > This ioctl is used when radar is delected on a channel. Data
> > frames must stop but management frames must be allowed to continue
> > for some time to communicate the channel switch to stations.
>
> Which does lead to the question: How are you detecting radar in
> userspace in the first place??
I've been working on merging Devicescape's 802.11h / radar detection
implementation into the open source hostapd (and the wireless-dev kernel).
Radar is initially detected by the low-level radio driver. Userspace
gets notified of radar via calls to ieee80211_radar_status, which
generates a "fake" management frame with a struct ieee80211_radar_info
in it. Userspace is then responsible for handling the resultant
activities, such as stopping transmission on that channel, selecting
another channel, sending out channel switch announcements, changing
channels, and remembering to block use of the old channel for the
required time.
I'll reply to your and Jiri's other question separately.
Thanks,
elliot
next prev parent reply other threads:[~2006-08-28 18:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060822173241.313859000@devicescape.com>
2006-08-22 17:33 ` [patch 1/5] d80211: allow for large scan results David Kimdon
2006-08-22 17:33 ` [patch 2/5] d80211: fix multiple device support David Kimdon
2006-08-22 17:33 ` [patch 3/5] d80211: fix interface removal David Kimdon
2006-08-23 7:20 ` Johannes Berg
2006-08-23 16:05 ` Jiri Benc
2006-08-22 17:34 ` [patch 4/5] d80211/bcm43xx: fix build for ARM David Kimdon
2006-08-22 18:58 ` Michael Buesch
2006-08-22 17:34 ` [patch 5/5] d80211: add ioctl to stop data frame tx David Kimdon
2006-08-23 7:25 ` Johannes Berg
2006-08-23 16:09 ` Jiri Benc
2006-08-28 18:34 ` Elliot Schwartz
2006-08-23 19:20 ` Simon Barber
2006-08-28 18:29 ` Elliot Schwartz [this message]
2006-08-29 7:30 ` Johannes Berg
2006-08-29 11:45 ` John W. Linville
2006-08-29 18:39 ` Jouni Malinen
2006-08-30 7:26 ` Johannes Berg
2006-08-30 16:01 ` Jouni Malinen
2006-08-31 7:23 ` Johannes Berg
2006-09-22 12:13 ` Jiri Benc
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=uwt8sww6z.fsf@devicescape.com \
--to=elliot@devicescape.com \
--cc=david.kimdon@devicescape.com \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linville@tuxdriver.com \
--cc=netdev@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).