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 09:45:24 +0200 [thread overview]
Message-ID: <1249026324.29587.15.camel@johannes.local> (raw)
In-Reply-To: <1249001028-15110-1-git-send-email-lrodriguez@atheros.com>
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
On Thu, 2009-07-30 at 17:43 -0700, Luis R. Rodriguez wrote:
> By doing so though we also disallowed beacon hints on devices
> registering their wiphy with custom world regulatory domains
> enabled, this happens to be currently ath5k, ath9k and ar9170.
> The passive scan and beacon restrictions on those devices would
> never be lifted even if we did find a beacon and the hardware did
> support such enhancements when world roaming.
I dislike this solution, it just adds proliferation of possible
behaviours. Can't those devices just set the _flags_ in their reg
notifier, and clear the corresponding bit in the orig_flags?
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 7:45 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 [this message]
2009-07-31 15:49 ` Luis R. Rodriguez
2009-07-31 15:56 ` Johannes Berg
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=1249026324.29587.15.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