All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mihai Moldovan <ionic@ionic.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9380 + hostapd + HT over 802.11a
Date: Tue, 31 May 2011 21:36:57 +0200	[thread overview]
Message-ID: <4DE54359.6060309@ionic.de> (raw)
In-Reply-To: <4DE535A1.7030108@ionic.de>

* On 31.05.2011 08:38 PM, Mihai Moldovan wrote:
> Rebuilding the Kernel soon... well as soon as I revert the regd.c patch. :)

Hmm, new patch, but also some bad news: all 5Ghz channels are AP-locked 
when using German regdomain, most of them even disabled. iw list:

Frequencies:
                         * 5180 MHz [36] (18.0 dBm) (passive scanning, 
no IBSS)
                         * 5200 MHz [40] (18.0 dBm) (passive scanning, 
no IBSS)
                         * 5220 MHz [44] (18.0 dBm) (passive scanning, 
no IBSS)
                         * 5240 MHz [48] (18.0 dBm) (passive scanning, 
no IBSS)
                         * 5260 MHz [52] (disabled)
                         * 5280 MHz [56] (disabled)
                         * 5300 MHz [60] (disabled)
                         * 5320 MHz [64] (disabled)
                         * 5500 MHz [100] (disabled)
                         * 5520 MHz [104] (disabled)
                         * 5540 MHz [108] (disabled)
                         * 5560 MHz [112] (disabled)
                         * 5580 MHz [116] (disabled)
                         * 5600 MHz [120] (disabled)
                         * 5620 MHz [124] (disabled)
                         * 5640 MHz [128] (disabled)
                         * 5660 MHz [132] (disabled)
                         * 5680 MHz [136] (disabled)
                         * 5700 MHz [140] (disabled)
                         * 5745 MHz [149] (18.0 dBm) (passive scanning, 
no IBSS)
                         * 5765 MHz [153] (18.0 dBm) (passive scanning, 
no IBSS)
                         * 5785 MHz [157] (18.0 dBm) (passive scanning, 
no IBSS)
                         * 5805 MHz [161] (18.0 dBm) (passive scanning, 
no IBSS)
                         * 5825 MHz [165] (18.0 dBm) (passive scanning, 
no IBSS)

That's weird, as we do have 802.11n up to 300MBit/s routers here, so I 
can't believe it's locked due to legal regulations. My university is 
running some of those WLAN APs, for instance.



Adapted patch against 2.6.38.6:

diff -uhr linux-2.6.38.6-orig/drivers/net/wireless/ath/ath9k/init.c 
linux-2.6.38.6/drivers/net/wireless/ath/ath9k/init.c
--- linux-2.6.38.6-orig/drivers/net/wireless/ath/ath9k/init.c 
2011-05-10 00:16:23.000000000 +0200
+++ linux-2.6.38.6/drivers/net/wireless/ath/ath9k/init.c 
2011-05-31 21:01:51.253906201 +0200
@@ -33,6 +33,11 @@
  module_param_named(nohwcrypt, ath9k_modparam_nohwcrypt, int, 0444);
  MODULE_PARM_DESC(nohwcrypt, "Disable hardware encryption");

+static int modparam_override_eeprom_regdomain = -1;
+module_param_named(override_eeprom_regdomain,
+                   modparam_override_eeprom_regdomain, int, S_IRUGO);
+MODULE_PARM_DESC(override_eeprom_regdomain, "Override regdomain 
hardcoded in EEPROM with this value (DANGEROUS).");
+
  int led_blink;
  module_param_named(blink, led_blink, int, 0444);
  MODULE_PARM_DESC(blink, "Enable LED blink on activity");
@@ -635,6 +640,7 @@
  void ath9k_set_hw_capab(struct ath_softc *sc, struct ieee80211_hw *hw)
  {
         struct ath_common *common = ath9k_hw_common(sc->sc_ah);
+        struct ath_regulatory *regulatory = 
ath9k_hw_regulatory(sc->sc_ah);

         hw->flags = IEEE80211_HW_RX_INCLUDES_FCS |
                 IEEE80211_HW_HOST_BROADCAST_PS_BUFFERING |
@@ -688,6 +694,14 @@
                         setup_ht_cap(sc, 
&sc->sbands[IEEE80211_BAND_5GHZ].ht_cap);
         }

+        if (modparam_override_eeprom_regdomain != -1) {
+                printk(KERN_ERR "ath9k: DANGER! You're overriding 
EEPROM-defined regulatory domain.\n");
+                printk(KERN_ERR "ath9k: Your card was not certified to 
operate on the domain you choosed.\n");
+                printk(KERN_ERR "ath9k: This might result in a 
violation of your local regulatory rules.\n");
+                printk(KERN_ERR "ath9k: Do not ever do that unless you 
really know what you do!\n");
+                regulatory->current_rd = 
modparam_override_eeprom_regdomain;
+        }
+
         SET_IEEE80211_PERM_ADDR(hw, common->macaddr);
  }


I guess

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6111 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110531/5d530e26/attachment-0001.bin 

  parent reply	other threads:[~2011-05-31 19:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 17:36 [ath9k-devel] AR9380 + hostapd + HT over 802.11a Mihai Moldovan
2011-05-31 17:56 ` Peter Stuge
2011-05-31 18:17   ` Mihai Moldovan
2011-05-31 18:06 ` Ben Greear
2011-05-31 18:29   ` Mihai Moldovan
2011-05-31 18:33     ` Ben Greear
2011-05-31 18:38       ` Mihai Moldovan
2011-05-31 18:39         ` Mihai Moldovan
2011-05-31 19:36         ` Mihai Moldovan [this message]
2011-05-31 19:48           ` Ben Greear
2011-05-31 20:00             ` Mihai Moldovan
2011-06-01  7:01               ` Mihai Moldovan
2011-06-01 14:31                 ` Mihai Moldovan
2011-06-01 14:45                   ` Mihai Moldovan
2011-06-01 17:53               ` Ben Greear
2011-06-01 18:37                 ` Mihai Moldovan

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=4DE54359.6060309@ionic.de \
    --to=ionic@ionic.de \
    --cc=ath9k-devel@lists.ath9k.org \
    /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.