From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Cc: Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless@vger.kernel.org
Subject: [BUG] iwlwifi need to correct channels info
Date: Fri, 28 Jan 2011 16:41:00 +0100 [thread overview]
Message-ID: <20110128154100.GB2452@redhat.com> (raw)
After commit 59eb21a6504731fc16db4cf9463065dd61093e08
"cfg80211: Extend channel to frequency mapping for 802.11j"
5GHz networks are not seen on scan results.
I think above commit is correct, but we have broken channel
information on iwlwifi (freq is 0 on 5GHz channels):
Channel 1 Freq=2412[2.4GHz] valid flag=0x20
Channel 2 Freq=2417[2.4GHz] valid flag=0x20
Channel 3 Freq=2422[2.4GHz] valid flag=0x20
Channel 4 Freq=2427[2.4GHz] valid flag=0x20
Channel 5 Freq=2432[2.4GHz] valid flag=0x0
Channel 6 Freq=2437[2.4GHz] valid flag=0x0
Channel 7 Freq=2442[2.4GHz] valid flag=0x0
Channel 8 Freq=2447[2.4GHz] valid flag=0x10
Channel 9 Freq=2452[2.4GHz] valid flag=0x10
Channel 10 Freq=2457[2.4GHz] valid flag=0x10
Channel 11 Freq=2462[2.4GHz] valid flag=0x10
Channel 12 Freq=2467[2.4GHz] valid flag=0x36
Channel 13 Freq=2472[2.4GHz] valid flag=0x36
Channel 36 Freq=0[5.2GHz] valid flag=0x26
Channel 40 Freq=0[5.2GHz] valid flag=0x16
Channel 44 Freq=0[5.2GHz] valid flag=0x26
Channel 48 Freq=0[5.2GHz] valid flag=0x16
Channel 52 Freq=0[5.2GHz] valid flag=0x2E
Channel 56 Freq=0[5.2GHz] valid flag=0x1E
Channel 60 Freq=0[5.2GHz] valid flag=0x2E
Channel 64 Freq=0[5.2GHz] valid flag=0x1E
Channel 100 Freq=0[5.2GHz] valid flag=0x2E
Channel 104 Freq=0[5.2GHz] valid flag=0x1E
Channel 108 Freq=0[5.2GHz] valid flag=0x2E
Channel 112 Freq=0[5.2GHz] valid flag=0x1E
Channel 116 Freq=0[5.2GHz] valid flag=0x2E
Channel 120 Freq=0[5.2GHz] valid flag=0x1E
Channel 124 Freq=0[5.2GHz] valid flag=0x2E
Channel 128 Freq=0[5.2GHz] valid flag=0x1E
Channel 132 Freq=0[5.2GHz] valid flag=0x2E
Channel 136 Freq=0[5.2GHz] valid flag=0x1E
Channel 140 Freq=0[5.2GHz] valid flag=0x3E
Channel 149 Freq=0[5.2GHz] valid flag=0x26
Channel 153 Freq=0[5.2GHz] valid flag=0x16
Channel 157 Freq=0[5.2GHz] valid flag=0x26
Channel 161 Freq=0[5.2GHz] valid flag=0x16
Channel 165 Freq=0[5.2GHz] valid flag=0x36
next reply other threads:[~2011-01-28 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 15:41 Stanislaw Gruszka [this message]
2011-01-28 18:06 ` [BUG] iwlwifi need to correct channels info Johannes Berg
2011-01-31 9:38 ` Stanislaw Gruszka
2011-01-31 10:53 ` Johannes Berg
2011-01-31 11:33 ` Stanislaw Gruszka
2011-01-31 10:44 ` Bruno Randolf
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=20110128154100.GB2452@redhat.com \
--to=sgruszka@redhat.com \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wey-yi.w.guy@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 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.