All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Copeland <me@bobcopeland.com>
To: Andrey Yurovsky <andrey@cozybit.com>
Cc: Hans Maes <Hans@bitnet.be>, linux-wireless@vger.kernel.org
Subject: Re: current status of 802.11s mesh in ath5k ?
Date: Fri, 19 Jun 2009 13:19:54 -0400	[thread overview]
Message-ID: <b6c5339f0906191019ve40014dp98af5ada875e2a24@mail.gmail.com> (raw)
In-Reply-To: <45e8e6c40906191000i2e74e06btee7313c5c30bc6a2@mail.gmail.com>

On Fri, Jun 19, 2009 at 1:00 PM, Andrey Yurovsky<andrey@cozybit.com> wrote:
> You'll want wireless-testing (or the latest compat), after commit
> 41ba08509.  However ath5k will not beacon until you issue a scan due
> to a bug.

By the way, I imagine this is a side effect of calling ath5k_beacon_config
inside ath5k_reset().  If so, we probably want to call it at the
appropriate time when the interface is brought up.

I have been working on a patch to rework the beaconing, namely using
bss_conf->enable_beacon and calling beacon_config whenever the beacon
interval or beacon changes, that might fix it but I'm not too familiar
with mesh details to say.

-- 
Bob Copeland %% www.bobcopeland.com

  reply	other threads:[~2009-06-19 17:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19  9:32 current status of 802.11s mesh in ath5k ? Hans Maes
2009-06-19 17:00 ` Andrey Yurovsky
2009-06-19 17:19   ` Bob Copeland [this message]
2009-06-19 17:42     ` Andrey Yurovsky
2009-07-05 12:05       ` Bob Copeland
2009-07-07 18:42         ` Andrey Yurovsky
2009-06-20  0:58   ` Hans Maes
2009-06-20  9:32     ` Nick Kossifidis
2009-06-22 16:59       ` Stephane Davy

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=b6c5339f0906191019ve40014dp98af5ada875e2a24@mail.gmail.com \
    --to=me@bobcopeland.com \
    --cc=Hans@bitnet.be \
    --cc=andrey@cozybit.com \
    --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.