From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
Jouni Malinen <jouni.malinen@atheros.com>
Subject: Re: [PATCH] cfg80211: fix regression on beacon world roaming feature
Date: Fri, 31 Jul 2009 17:56:22 +0200 [thread overview]
Message-ID: <1249055782.20312.19.camel@johannes.local> (raw)
In-Reply-To: <43e72e890907310849l3487b8a2p52302f6662a26f95@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
On Fri, 2009-07-31 at 08:49 -0700, Luis R. Rodriguez wrote:
> > just set the _flags_ in their reg
> > notifier,
>
> So if you mean devices that used custom reg stuff, the answer is no
> because the patch which introduced the regression would prevent the
> setting of the passive scan flag and beaconing restrictions so the
> reg_notifier would never notice the difference.
I did mean those devices. Adding a reg notifier hook for iwlwifi seems a
little odd, given that cfg80211 is supposed to always honour the flags
(which it copies to orig_flags for that purpose).
But I don't see why ath couldn't do this:
* do _not_ set the passive/no-ibss flags in flags (orig_flags)
* in the reg notifier, always set the passive/no-ibss flag into 'flags'
unless a beacon was noticed on that channel.
What am I missing?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-07-31 15:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 0:43 [PATCH] cfg80211: fix regression on beacon world roaming feature Luis R. Rodriguez
2009-07-31 7:45 ` Johannes Berg
2009-07-31 15:49 ` Luis R. Rodriguez
2009-07-31 15:56 ` Johannes Berg [this message]
2009-07-31 16:03 ` Luis R. Rodriguez
2009-07-31 16:11 ` Johannes Berg
2009-07-31 16:32 ` Luis R. Rodriguez
2009-07-31 16:43 ` Johannes Berg
2009-07-31 17:28 ` Luis R. Rodriguez
2009-07-31 17:30 ` Luis R. Rodriguez
2009-07-31 17:52 ` Johannes Berg
2009-07-31 17:59 ` Luis R. Rodriguez
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=1249055782.20312.19.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=jouni.malinen@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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