From: Hauke Mehrtens <hauke@hauke-m.de>
To: "W. Trevor King" <wking@tremily.us>
Cc: arend@broadcom.com, linux-wireless@vger.kernel.org,
brcm80211-dev-list@broadcom.com
Subject: Re: [RFC 12/13] brcmsmac: add support for probe response template
Date: Sun, 24 Feb 2013 10:39:25 +0100 [thread overview]
Message-ID: <5129DFCD.3020009@hauke-m.de> (raw)
In-Reply-To: <20130224023008.GG1361@odin.tremily.us>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/24/2013 03:30 AM, W. Trevor King wrote:
> On Sun, Feb 24, 2013 at 02:06:10AM +0100, Hauke Mehrtens wrote:
>> The ucode is able to answer probe response by itself. This writes
>> such a template into the specific memory. Currently the probe
>> requests are also send to mac80211 so there are more answers send
>> to a requesting client. We have to make the ucode stop sending
>> probe requests to the driver.
>
> Should this read "so there are more answers sent to"?
>
yes there are more answers then normal send out, but it is normal that
you send out more than one, at least I have seen it so it is probably
in the standard. The last part of this patch could applied again to
not receive probe requests any more:
http://driverdev.linuxdriverproject.org/pipermail/devel/2011-October/021574.html
Hauke
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQIcBAEBAgAGBQJRKd/JAAoJEIZ0px9YPRMyNa8QAJtd4fqHhJy+uH+yzc5OKezu
z4bHbKidWek6quLJz+34zo8hMMebnVWb+PxtKkbfN3XiRfFvggOuGRqgY73mWe8d
UctlXnnV292h+QBIYr6exrv4WoqFISiGKyvudTS0aHeLLq9S4slVXRYiEkJT9tdW
Lc/ccl9rg9QYAOkZcdJaNDp+MwZ3WA+fJvGXQiVwYKzGoAt6tUZZkZHs3yHQBCe1
rq3nITwXPRxor+3ba/2ws9mIcZAbGSf6eIOxdwC7JSoP2D8QvYU3pUvR9h79NtlB
2EXOo9PuzPnG8cpcFDi44iZGNf9Kjw4eoZ9JjfrbfXNhx7ucf8wjVNehVyPFivr0
PlptGecxs08UnfCQXBH+cpvlMjE+8kj1gxmPRkD0Z+ghgY801bHmbzprd8mOFyYY
TMqOlAUZtJgemPfYko/4ZaYeCZmMF1oFiDOUs3jkodAGU++TI/IG/DD7K5ZtPjBJ
0OzV1lr5YvOBUIXlhQQQYpF1IfIShyhcRwVPA9ZM5HvQHkKRbx8tF7QeqeOcdrn4
1tGg+Zrr9nc0UcS8ropnPRwjqDjCOna7F6aIaLZOm+D5WFX9ieWNbPx21s1Fo4fW
cf7VOvLZ/oWuJ0yrnbGQ/SBq0RvWF4zxSRQqXpZsu8CJnQZdeloq0REIooQK9Tl6
KgjpbASoKSVGBAI0w8RT
=v7yy
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-02-24 9:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 1:05 [RFC 00/13] brcmsmac: add AP mode Hauke Mehrtens
2013-02-24 1:05 ` [RFC 01/13] brcmsmac: implement ieee80211_ops get_tsf and set_tsf Hauke Mehrtens
2013-02-24 1:06 ` [RFC 02/13] brcmsmac: add interface type to brcms_bss_cfg Hauke Mehrtens
2013-02-24 1:06 ` [RFC 03/13] brcmsmac: remove brcms_bss_cfg->BSS Hauke Mehrtens
2013-02-24 1:06 ` [RFC 04/13] brcmsmac: remove brcms_bss_cfg->associated Hauke Mehrtens
2013-02-24 1:06 ` [RFC 05/13] brcmsmac: remove brcms_bss_cfg->enable Hauke Mehrtens
2013-02-24 1:06 ` [RFC 06/13] brcmsmac: remove brcms_bss_cfg->up Hauke Mehrtens
2013-02-24 1:06 ` [RFC 07/13] brcmsmac: remove brcms_bss_cfg->cur_etheraddr Hauke Mehrtens
2013-02-24 1:06 ` [RFC 08/13] brcmsmac: remove brcms_pub->bcmerr Hauke Mehrtens
2013-02-24 1:06 ` [RFC 09/13] brcmsmac: write beacon period to hardware Hauke Mehrtens
2013-02-24 1:06 ` [RFC 10/13] brcmsmac: add beacon template support Hauke Mehrtens
2013-02-24 1:06 ` [RFC 11/13] brcmsmac: react on changing SSID Hauke Mehrtens
2013-02-24 1:06 ` [RFC 12/13] brcmsmac: add support for probe response template Hauke Mehrtens
2013-02-24 2:30 ` W. Trevor King
2013-02-24 9:39 ` Hauke Mehrtens [this message]
2013-02-24 15:06 ` W. Trevor King
2013-02-24 1:06 ` [RFC 13/13] brcmsmac: activate AP support Hauke Mehrtens
2013-02-24 2:30 ` W. Trevor King
2013-02-24 9:41 ` Hauke Mehrtens
2013-02-24 10:21 ` [RFC 00/13] brcmsmac: add AP mode Arend Van Spriel
2013-02-24 11:38 ` Hauke Mehrtens
2013-02-24 15:25 ` Hauke Mehrtens
2013-02-24 17:22 ` Johannes Berg
2013-02-24 22:31 ` Hauke Mehrtens
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=5129DFCD.3020009@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wking@tremily.us \
/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).