From: Bruno Randolf <br1@einfach.org>
To: Javier Cardona <javier@cozybit.com>
Cc: Bob Copeland <me@bobcopeland.com>,
"John W. Linville" <linville@tuxdriver.com>,
Steve Derosier <steve@cozybit.com>,
devel@lists.open80211s.org, linux-wireless@vger.kernel.org,
Jiri Slaby <jirislaby@gmail.com>,
Nick Kossifidis <mickflemm@gmail.com>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: Re: [PATCH 1/3] ath5k: Fix beaconing in mesh mode
Date: Thu, 2 Dec 2010 10:16:31 +0900 [thread overview]
Message-ID: <201012021016.31876.br1@einfach.org> (raw)
In-Reply-To: <AANLkTikNQitSrcj4Zn++BRAKp46hYTFb0tw61oD_bGVx@mail.gmail.com>
On Thu December 2 2010 03:23:07 Javier Cardona wrote:
> > Do you need to update the beacon this often or just once?
> > Adhoc doesn't need to do this, for example, because it doesn't
> > need the TIM; I don't know about mesh.
>
> Currently power save mode is not implemented for mesh interfaces, so
> the TIM is not really updated or used. But yes, in principle mesh
> beacons should include the TIM. So it's better to use AP style
> beaconing to pave the way for someone implementing proper traffic info
> maps and power save for mesh.
I have been thinking the same. Using the same style beaconing for AP, ad-hoc
and mesh mode could simplify the code, and make it easier to implement TIM or
DFS later.
bruno
next prev parent reply other threads:[~2010-12-02 1:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 2:18 ath5k: Fixes for mesh operation Javier Cardona
2010-12-01 2:18 ` [PATCH 1/3] ath5k: Fix beaconing in mesh mode Javier Cardona
2010-12-01 13:16 ` Bob Copeland
2010-12-01 18:23 ` Javier Cardona
2010-12-02 1:16 ` Bruno Randolf [this message]
2010-12-07 20:58 ` John W. Linville
2010-12-07 21:35 ` Javier Cardona
2010-12-01 2:18 ` [PATCH 2/3] ath5k: Prevent mesh interfaces from being counted as ad-hoc Javier Cardona
2010-12-07 20:58 ` John W. Linville
2010-12-07 21:36 ` Javier Cardona
2010-12-01 2:18 ` [PATCH 3/3] ath5k: Put the right tsf value in mesh beacons Javier Cardona
2010-12-07 20:57 ` John W. Linville
2010-12-07 21:37 ` Javier Cardona
2010-12-07 19:12 ` ath5k: Fixes for mesh operation Javier Cardona
2010-12-07 20:57 ` John W. Linville
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=201012021016.31876.br1@einfach.org \
--to=br1@einfach.org \
--cc=devel@lists.open80211s.org \
--cc=javier@cozybit.com \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=me@bobcopeland.com \
--cc=mickflemm@gmail.com \
--cc=steve@cozybit.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).