From: Matthieu CASTET <castet.matthieu@free.fr>
To: linux-wireless@vger.kernel.org
Subject: Re: B43 no beacon ?
Date: Tue, 12 May 2009 22:39:56 +0000 (UTC) [thread overview]
Message-ID: <loom.20090512T223807-343@post.gmane.org> (raw)
In-Reply-To: loom.20090511T202208-851@post.gmane.org
Hi,
after some tracing, it seems to BSS_CHANGED_BSSID flag is never set and we never
call b43_update_templates.
Removing the changed & BSS_CHANGED_BSSID check (from [1]) make the beacon work
Matthieu
[1]
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next-2.6.git;a=commitdiff;h=2d0ddec5b2b859f06116f631fc0ffe94fbceb556
next prev parent reply other threads:[~2009-05-12 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 20:31 B43 no beacon ? Matthieu CASTET
2009-05-12 22:39 ` Matthieu CASTET [this message]
2009-05-18 8:53 ` [PATCH] b43/legacy: fix beacon change processing Johannes Berg
2009-05-18 18:19 ` Michael Buesch
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=loom.20090512T223807-343@post.gmane.org \
--to=castet.matthieu@free.fr \
--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 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).