All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Arend Van Spriel <arend@broadcom.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	brcm80211-dev-list <brcm80211-dev-list@broadcom.com>
Subject: Re: [RFC 00/13] brcmsmac: add AP mode
Date: Sun, 24 Feb 2013 23:31:15 +0100	[thread overview]
Message-ID: <512A94B3.4020205@hauke-m.de> (raw)
In-Reply-To: <1361726563.8129.6.camel@jlt4.sipsolutions.net>

On 02/24/2013 06:22 PM, Johannes Berg wrote:
> On Sun, 2013-02-24 at 12:38 +0100, Hauke Mehrtens wrote:
> 
>> Yes this needs some review and more testing, I hope this also works with
>> power saving stations and so on.
> 
> I doubt it will. I know it's not really a major thing, but due to the
> way aggregation is handled you definitely need to implement
> "release_buffered_frames". "allow_buffered_frames" might not be
> necessary if the device doesn't track station's powersave mode by
> itself? Not sure how that's supposed to work, too long since I worked on
> Broadcom stuff.

Ok, I have to read how power saving exactly works and look how brcmsmac
currently does aggregation and so on.

>> probe response offload
> 
> See also enum nl80211_probe_resp_offload_support_attr; probe response
> offload is a bit tricky because e.g. for WPS you absolutely need
> userspace, not the firmware, to respond. So if the firmware can't tell
> the difference between regular and WPS probe requests, you can't support
> WPS.
> 
> If you can, I'd probably just turn off the response offload. It's likely
> not worth the effort. If you wanted to make that turning off conditional
> we'd have to come up with a bunch of new API to let the driver know what
> kind of AP it's running.

Ok, I will turn it off, this driver is mostly used on devices without a
battery, or a big one, so the energy saving by offloading is not needed
and the performance improvement is probably not that big.

Hauke

      reply	other threads:[~2013-02-24 22:31 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
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 [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=512A94B3.4020205@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=arend@broadcom.com \
    --cc=brcm80211-dev-list@broadcom.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 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.