From: Bob Copeland <me@bobcopeland.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Christian Lamparter <chunkeey@web.de>,
Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] ath9k's regulatory domain code changes (for ar9170)
Date: Sun, 29 Mar 2009 15:39:00 -0400 [thread overview]
Message-ID: <20090329193900.GA27166@hash.localnet> (raw)
In-Reply-To: <43e72e890903242045n520842c3q9392f75651a6b905@mail.gmail.com>
On Tue, Mar 24, 2009 at 08:45:53PM -0700, Luis R. Rodriguez wrote:
> > Fixed..
> >
> > http://bombadil.infradead.org/~mcgrof/patches/ath/ath-common-v5.patch.txt
>
> Nope.. no luck, something got messed up along the way... needs a closer look.
So I tested this series and it works fine, with a caveat:
Currently, ath5k exposes tons of 5 GHz channels. In addition to the other
problems I mentioned in http://marc.info/?l=linux-wireless&m=123825852320853,
it also essentially breaks with regulatory hints from the driver. This is
because because the Atheros world regdomain allows most channels in the
5 GHz range for passive scanning, whereas the default world regdomain
disables many of these. Consequently, scanning takes long enough that
NM/wpa_supplicant bails.
So, I think the way forward is to include the patch linked above with the
rest of the series. Although perhaps the last patch moving ath5k/ath9k etc
under the ath/ directory can be put off a while in case people have patches
sitting around against the old dir structure.
Anyone who still wants to use all the channels with ath5k can use a custom
regd or configure the supplicant to scan the specific channels they are
interested in.
--
Bob Copeland %% www.bobcopeland.com
prev parent reply other threads:[~2009-03-29 19:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 18:38 [RFC] ath9k's regulatory domain code changes (for ar9170) Christian Lamparter
2009-03-24 18:59 ` Bob Copeland
2009-03-24 18:41 ` Luis R. Rodriguez
2009-03-24 20:03 ` Bob Copeland
2009-03-24 20:10 ` Luis R. Rodriguez
2009-03-24 20:31 ` Johannes Berg
2009-03-24 22:04 ` Luis R. Rodriguez
2009-03-28 16:39 ` Bob Copeland
2009-03-29 23:13 ` Nick Kossifidis
2009-03-29 23:15 ` Nick Kossifidis
2009-03-30 12:00 ` Bob Copeland
2009-03-24 20:33 ` Christian Lamparter
2009-03-24 20:58 ` Luis R. Rodriguez
2009-03-24 22:09 ` Bob Copeland
2009-03-24 21:14 ` Luis R. Rodriguez
2009-03-24 22:24 ` Christian Lamparter
2009-03-24 22:30 ` Bob Copeland
2009-03-24 23:13 ` Luis R. Rodriguez
2009-03-24 23:17 ` Luis R. Rodriguez
2009-03-24 23:52 ` Luis R. Rodriguez
2009-03-25 1:06 ` Bob Copeland
2009-03-25 2:30 ` Luis R. Rodriguez
2009-03-25 2:59 ` Luis R. Rodriguez
2009-03-25 3:15 ` Luis R. Rodriguez
2009-03-25 3:45 ` Luis R. Rodriguez
2009-03-29 19:39 ` Bob Copeland [this message]
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=20090329193900.GA27166@hash.localnet \
--to=me@bobcopeland.com \
--cc=chunkeey@web.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--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 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.