From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Dan Williams <dcbw@redhat.com>,
John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
j@w1.fi
Subject: Re: [PATCH] mac80211: add pre- and post-scan hooks
Date: Thu, 11 Sep 2008 23:35:38 +0300 [thread overview]
Message-ID: <48C9811A.7070206@w1.fi> (raw)
In-Reply-To: <1221159194.6986.57.camel@johannes.berg>
Johannes Berg wrote:
> The beaconing API in total is a bit strange, we tell the driver when the
> beacon changes and it can then request one, but we never tell it when to
> start/stop beaconing, which means that currently your driver has to
> figure to start out beaconing on the first beacon change, and then
> cannot possibly stop again... We can return NULL from the beacon get
> function but that could be an error condition too...
The original design was for AP mode only and the assumption was that
Beacon transmission is enabled pretty much all the time. Returning NULL
was used if ever needed to stop Beacon transmission for some period of
time.
> I think we just need to add start/stop beacon bits, and then we can use
> them around a scan too, thoughts?
That sounds reasonable.
- Jouni
next prev parent reply other threads:[~2008-09-11 20:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 15:43 [PATCH] mac80211: add pre- and post-scan hooks Dan Williams
2008-06-24 8:55 ` Johannes Berg
2008-06-24 11:15 ` Dan Williams
2008-06-24 11:21 ` Johannes Berg
2008-06-24 14:45 ` Dan Williams
2008-06-24 14:53 ` Johannes Berg
2008-09-10 7:51 ` Johannes Berg
2008-09-10 13:09 ` Dan Williams
2008-09-10 21:38 ` Johannes Berg
2008-09-11 18:53 ` Johannes Berg
2008-09-11 20:35 ` Jouni Malinen [this message]
2008-09-11 23:26 ` 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=48C9811A.7070206@w1.fi \
--to=j@w1.fi \
--cc=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).