linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Pat Erley <pat-lkml@erley.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	ath9k-devel@lists.ath9k.org, andrey@cozybit.com,
	Andrey Yurovsky <andrey@cozybit.com>,
	brian@cozybit.com, javier@cozybit.com, colin@cozybit.com
Subject: Re: [rfc] Implement ath9k mesh point operation
Date: Tue, 17 Mar 2009 08:46:07 +0100	[thread overview]
Message-ID: <1237275967.18086.6.camel@johannes.local> (raw)
In-Reply-To: <49BED464.2010904@erley.org> (sfid-20090316_233631_951441_68D057DC)

[-- Attachment #1: Type: text/plain, Size: 493 bytes --]

On Mon, 2009-03-16 at 18:36 -0400, Pat Erley wrote:

> Currently, you need to trigger a scan on the mesh point interface to
> enable beaconing.  This is the same behavior the ath5k, rt2500usb and 
> rt61pci drivers exhibit.  Is this a mac80211 design flaw, or something
> in all of these drivers?

It's mac80211. We never call ieee80211_if_config() when we enable a mesh
interface, and thus conf.enable_beacon with
IEEE80211_IFCC_BEACON_ENABLED isn't ever set correctly.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2009-03-17  7:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 22:36 [rfc] Implement ath9k mesh point operation Pat Erley
2009-03-16 22:57 ` Andrey Yurovsky
2009-03-16 23:03   ` Pat Erley
2009-03-17  4:45 ` Pat Erley
2009-03-17  7:44   ` Johannes Berg
2009-03-17  7:46 ` Johannes Berg [this message]
2009-03-17 21:05   ` Andrey Yurovsky

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=1237275967.18086.6.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=andrey@cozybit.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=brian@cozybit.com \
    --cc=colin@cozybit.com \
    --cc=javier@cozybit.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pat-lkml@erley.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 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).