From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
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:51:43 +0100 [thread overview]
Message-ID: <1225983103.3619.242.camel@johannes.berg> (raw)
In-Reply-To: <1ba2fa240811060647x688f1efp1728e5f80dbb6b35@mail.gmail.com> (sfid-20081106_154710_192457_283691F4)
[-- Attachment #1: Type: text/plain, Size: 560 bytes --]
On Thu, 2008-11-06 at 16:47 +0200, Tomas Winkler wrote:
> The problem with missing A band is that this info was supplied to
> driver too late. after registration otherwise
> the iwlwifi dealt properly with missing band This was change in design
> that wasn't reflected in the driver.
>
> This can happen _regardless_ of the setting of old regulatory,
>
> With old regulatory the channel was known prior to registration
Ah, you mean the driver wasn't updated (and previously not prepared) to
handle changing regulatory information?
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:51 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
2008-11-06 14:40 ` Johannes Berg
2008-11-06 14:47 ` Tomas Winkler
2008-11-06 14:51 ` Johannes Berg [this message]
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=1225983103.3619.242.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=tomasw@gmail.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).