All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Ivo van Doorn <ivdoorn@gmail.com>,
	Gertjan van Wingerde <gwingerde@gmail.com>
Subject: Re: rt2x00 & mac80211: correct usage of ieee80211_beacon_get_tim?
Date: Thu, 24 Jun 2010 18:20:03 +0200	[thread overview]
Message-ID: <201006241820.03539.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <1277394714.3870.8.camel@jlt3.sipsolutions.net>

Am Donnerstag 24 Juni 2010 schrieb Johannes Berg:
>  a) You get a new beacon from mac80211 each time you send it. Then you
>     don't have to worry about the set_tim() callback at all -- don't
>     assign it!
> 
>  b) You need to get a new beacon frame from mac80211 only when it
>     changes. You can do this from set_tim(). HOWEVER: since you're not
>     getting a new one from mac80211 all the time anyway, you NEED to
>     have the driver or firmware overwrite the DTIM count, like b43's
>     firmware for example will do.
> 
> Ok so maybe there are more possibilities like the firmware filling the
> TIM IE differently and you would use set_tim() differently then.
> 
> However, *fundamentally*, any time you don't get a new skb from mac80211
> for each transmitted beacon you NEED to overwrite the DTIM count in it.

So, to answer my own question:

mac80211 behaves as designed and we need to fix rt2x00 to correctly update
the DTIM parameters when we stick to the set_tim callback for updating the
beacon template (option b).

Or we would implement option a) to get a new beacon prior to transmission
and would get a correct DTIM count from mac80211.

Thanks for the clarification,
Helmut

  parent reply	other threads:[~2010-06-24 16:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-24 13:21 rt2x00 & mac80211: correct usage of ieee80211_beacon_get_tim? Helmut Schaa
2010-06-24 14:32 ` John W. Linville
2010-06-24 15:51 ` Johannes Berg
2010-06-24 15:53   ` Johannes Berg
2010-06-24 15:54     ` Johannes Berg
2010-06-24 16:20   ` Helmut Schaa [this message]
2010-06-25 16:01   ` Helmut Schaa
2010-06-26 15:32     ` John W. Linville
2010-06-27  8:21     ` Johannes Berg
2010-06-27 19:00       ` Helmut Schaa
2010-07-02 17:12         ` Johannes Berg
2010-07-02 17:59           ` Helmut Schaa
2010-07-02 18:06             ` Johannes Berg
2010-07-02 18:20               ` Helmut Schaa

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=201006241820.03539.helmut.schaa@googlemail.com \
    --to=helmut.schaa@googlemail.com \
    --cc=gwingerde@gmail.com \
    --cc=ivdoorn@gmail.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.