All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Jouni Malinen <j@w1.fi>,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH v4 0/5] mac80211: beacon filtering
Date: Wed, 25 Mar 2009 22:08:29 +0200	[thread overview]
Message-ID: <871vsl1i2q.fsf@litku.valot.fi> (raw)
In-Reply-To: <1238010031.4320.164.camel@johannes.local> (Johannes Berg's message of "Wed\, 25 Mar 2009 20\:40\:31 +0100")

Johannes Berg <johannes@sipsolutions.net> writes:

> On Wed, 2009-03-25 at 21:34 +0200, Kalle Valo wrote:
>
>> > It has to be dynamic, no? Much of the information in there would be
>> > things wpa_supplicant is only interested in. If it was just the kernel
>> > code -- yes, we could just have a static list somewhere -- but much of
>> > the 11k things for instance are only useful for wpa_supplicant.
>> 
>> But if we already know what wpa_supplicant needs, can't we do the
>> first implementation with a static list? Sure, the dynamic list is
>> something we should aim for.
>
> True. The userspace part is easy to add though, just make it part of the
> assoc() nl80211 command. So we just need the static list for the
> mac80211 part.

Sounds easy enough.

>> Do we have any knowledge how different hardware support beacon
>> checksumming? I only know how stlc45xx does it.
>
> Not really... how about wl12xx?

Heh, I'm so focused on my thesis right now that forgot wl12xx
altogether :)

I haven't investigate wl12xx beacon filtering in detail yet, but below
is what I quickly found from the firmware interface header files.
Looks like just what we would have expected.


Name:       ACX_BEACON_FILTER_TABLE

Desc: This information element configures beacon filtering handling
      for the set of information elements. An information element in a
      beacon can be set to be: ignored (never compared, and changes
      will not cause beacon transfer), checked (compared, and
      transferred in case of a change), or transferred (transferred to
      the host for each appearance or disappearance).

      The table contains all information elements that are subject to
      monitoring for host transfer.

      All information elements that are not in the table should be
      ignored for monitoring.

      This functionality is only enabled when beacon filtering is enabled by 
      ACX_BEACON_FILTER_OPT.

         Type:   Filtering Configuration

         Access: Write Only

         Length: 101

         Notes:  the field measuring the value of received beacons for
                 which the device wakes up the host in
                 ACX_BEACON_FILTER_OPT does not affect this
                 information element.

http://android.git.kernel.org/?p=platform/system/wlan/ti.git;a=blob;f=sta_dk_4_0_4_32/common/src/hal/FirmwareApi/public_infoele.h;h=9a7d1c1203de4db83f700d8cc961cee04e7e5de9;hb=HEAD#l720

-- 
Kalle Valo

  reply	other threads:[~2009-03-25 20:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-22 19:56 [PATCH v4 0/5] mac80211: beacon filtering Kalle Valo
2009-03-22 19:57 ` [PATCH v4 1/5] mac80211: decrease execution of the associated timer Kalle Valo
2009-03-22 19:57 ` [PATCH v4 2/5] mac80211: track beacons separately from the rx path activity Kalle Valo
2009-03-22 19:57 ` [PATCH v4 3/5] mac80211: disable power save when scanning Kalle Valo
2009-03-22 19:57 ` [PATCH v4 4/5] cfg80211: add feature to hold bss Kalle Valo
2009-03-22 19:57 ` [PATCH v4 5/5] mac80211: add beacon filtering support Kalle Valo
2009-03-22 20:02 ` [PATCH] stlc45xx: " Kalle Valo
2009-03-22 20:15 ` [PATCH v4 0/5] mac80211: beacon filtering Johannes Berg
2009-03-22 20:29   ` Kalle Valo
2009-03-24 13:11 ` Johannes Berg
2009-03-25  9:01   ` Kalle Valo
2009-03-25  9:30     ` Johannes Berg
2009-03-25 19:34       ` Kalle Valo
2009-03-25 19:40         ` Johannes Berg
2009-03-25 20:08           ` Kalle Valo [this message]
2009-03-25 20:17             ` 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=871vsl1i2q.fsf@litku.valot.fi \
    --to=kalle.valo@iki.fi \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.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 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.