From: Larry Finger <Larry.Finger@lwfinger.net>
To: John Linville <linville@tuxdriver.com>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: The new regulatory code kills my wireless
Date: Fri, 12 Sep 2008 12:37:26 -0500 [thread overview]
Message-ID: <48CAA8D6.1030605@lwfinger.net> (raw)
After pulling the latest git from wireless-testing, my wireless
failed. I bisected this to be commit
544ec9a11fdef5142a76a8eb4b186a80a272c035, "cfg80211: Add new wireless
regulatory infrastructure". I have not yet implemented CRDA, thus I
selected the CONFIG_WIRELESS_OLD_REGULATORY option.
The symptoms are that my devices (b43 and p54usb) receive no scan
information.
The pertinent dmesg output follows:
cfg80211: Using old static regulatory domain:
cfg80211: Regulatory domain: US
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(239200 KHz - 248200 KHz @ 4000 KHz), (600 mBi, 2700 mBm)
(516000 KHz - 520000 KHz @ 4000 KHz), (600 mBi, 2300 mBm)
(518000 KHz - 522000 KHz @ 4000 KHz), (600 mBi, 2300 mBm)
(520000 KHz - 524000 KHz @ 4000 KHz), (600 mBi, 2300 mBm)
(522000 KHz - 534000 KHz @ 4000 KHz), (600 mBi, 2300 mBm)
(572500 KHz - 584500 KHz @ 4000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
Thanks,
Larry
next reply other threads:[~2008-09-12 17:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 17:37 Larry Finger [this message]
2008-09-12 17:40 ` The new regulatory code kills my wireless Luis R. Rodriguez
2008-09-12 18:46 ` Larry Finger
2008-09-12 19:19 ` Luis R. Rodriguez
2008-09-12 20:22 ` Johannes Berg
2008-09-12 20:34 ` Luis R. Rodriguez
2008-09-12 20:59 ` Larry Finger
2008-09-12 21:15 ` Luis R. Rodriguez
2008-09-13 2:26 ` Marcel Holtmann
2008-09-13 8:33 ` Johannes Berg
2008-09-13 16:51 ` Marcel Holtmann
2008-09-14 0:52 ` John W. Linville
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=48CAA8D6.1030605@lwfinger.net \
--to=larry.finger@lwfinger.net \
--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;
as well as URLs for NNTP newsgroup(s).