From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Marcel Holtmann <holtmann@linux.intel.com>,
Reinette Chatre <reinette.chatre@intel.com>,
linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net,
Abhijeet Kolekar <abhijeet.kolekar@intel.com>,
Zhu Yi <yi.zhu@intel.com>
Subject: Re: [PATCH 1/2 2.6.28] iwlwifi : Fix channel scanning/association in 5Ghz band
Date: Thu, 06 Nov 2008 15:37:33 +0100 [thread overview]
Message-ID: <1225982253.3619.233.camel@johannes.berg> (raw)
In-Reply-To: <20081106134950.GB14184@tuxdriver.com> (sfid-20081106_153132_117397_0A76B85E)
[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]
On Thu, 2008-11-06 at 08:49 -0500, John W. Linville wrote:
> On Wed, Nov 05, 2008 at 11:17:22PM +0100, Marcel Holtmann wrote:
>
> >> This patch is related to bug 11870 at bugzilla.kernel.org. With
> >> correct regulatory information the number of channels to scan
> >> will be correct and not zero as seen in that bug.
> >>
> >> This patch eliminates the need for wireless to be compiled with
> >> CONFIG_WIRELESS_OLD_REGULATORY to get correct regulatory behavior with
> >> iwlwifi.
> >
> > so this is still for 2.6.28, but for 2.6.29 and wireless-testing the API
> > changed and we need a separate or different patch.
> >
> > John, Dave what is your take on pushing this to Linus this late in the
> > merge window? I personally think we should do that. And if not, then
> > change the Intel wireless Kconfig to select
> > CONFIG_WIRELESS_OLD_REGULATORY by default at least.
>
> CONFIG_WIRELESS_OLD_REGULATORY is already 'default y' now. I don't
> really see why iwlwifi should _require_ that if someone decides to
> choose a non-default configuration.
I agree, also, I thought the problem was that iwlwifi misbehaved if
there were no active channels in the 5 GHz band and there was a patch to
fix that? This can happen _regardless_ of the setting of old regulatory,
it just happens that without the setting, the default is no 5 GHz
channels, while with it the default has 5 GHz channels.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-11-06 14:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 19:14 [PATCH 1/2 2.6.28] iwlwifi : Fix channel scanning/association in 5Ghz band Reinette Chatre
2008-11-05 19:14 ` [PATCH 2/2 2.6.28] iwl3945 " Reinette Chatre
2008-11-05 22:17 ` [PATCH 1/2 2.6.28] iwlwifi " Marcel Holtmann
2008-11-05 22:41 ` reinette chatre
2008-11-06 1:07 ` Zhu Yi
2008-11-06 13:49 ` John W. Linville
2008-11-06 14:37 ` Johannes Berg [this message]
2008-11-06 14:40 ` Johannes Berg
2008-11-06 14:47 ` Tomas Winkler
2008-11-06 14:51 ` Johannes Berg
2008-11-06 14:54 ` Tomas Winkler
2008-11-06 14:58 ` Johannes Berg
2008-11-06 15:08 ` Tomas Winkler
2008-11-12 21:29 ` John W. Linville
2008-11-12 21:45 ` reinette chatre
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=1225982253.3619.233.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=abhijeet.kolekar@intel.com \
--cc=holtmann@linux.intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@intel.com \
--cc=yi.zhu@intel.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;
as well as URLs for NNTP newsgroup(s).