1. 10 2月, 2009 2 次提交
  2. 30 1月, 2009 2 次提交
    • L
      ath9k: fix debug print on regd · 0c6666e4
      Luis R. Rodriguez 提交于
      With debugging enabled and with ATH_DBG_REGULATORY
      selected we wouldn't get the full print out of one line,
      reason is we used "," instead of nothing to separate two
      lines.
      Signed-off-by: NLuis R. Rodriguez <lrodriguez@atheros.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      0c6666e4
    • L
      ath9k: simplify regulatory code · 5f8e077c
      Luis R. Rodriguez 提交于
      Now that cfg80211 has its own regulatory infrastructure we can
      condense ath9k's regulatory code considerably. We only keep data
      we need to provide our own regulatory_hint(), reg_notifier() and
      information necessary for calibration.
      
      Atheros hardware supports 12 world regulatory domains, since these
      are custom we apply them through the the new wiphy_apply_custom_regulatory().
      Although we have 12 we can consolidate these into 5 structures based on
      frequency and apply a different set of flags that differentiate them on
      a case by case basis through the reg_notifier().
      
      If CRDA is not found our own custom world regulatory domain is applied,
      this is identical to cfg80211's except we enable passive scan on most
      frequencies.
      Signed-off-by: NLuis R. Rodriguez <lrodriguez@atheros.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      5f8e077c
  3. 05 12月, 2008 3 次提交
  4. 07 8月, 2008 3 次提交