1. 29 1月, 2011 1 次提交
    • B
      ath: Add function to check if 4.9GHz channels are allowed · 5719efdd
      Bruno Randolf 提交于
      This adds a helper function to ath/regd.c which can be asked if 4.9GHz channels
      are allowed for a given regulatory domain code. This keeps the knowledge of
      regdomains and defines like MKK9_MKKC in one place. I'm passing the regdomain
      code instead of the ath_regulatory structure because this needs to be called
      quite early in the driver inititalization where ath_regulatory is not available
      yet in ath5k.
      
      I'm using MKK9_MKKC only because this is the regdomain in the 802.11j enabled
      sample cards we got from our vendor. I found some hints in HAL code that this
      is used by Atheros to indicate 4.9GHz channels support and that there might be
      other domain codes as well, but as I don't have any documentation I'm just
      putting in what I need right now. It can be extended later.
      Signed-off-by: NBruno Randolf <br1@einfach.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      5719efdd
  2. 01 9月, 2010 1 次提交
  3. 28 10月, 2009 1 次提交
  4. 09 9月, 2009 1 次提交
  5. 20 8月, 2009 1 次提交
  6. 23 4月, 2009 4 次提交
  7. 28 3月, 2009 1 次提交
  8. 17 3月, 2009 1 次提交
  9. 28 2月, 2009 4 次提交
  10. 14 2月, 2009 3 次提交
  11. 30 1月, 2009 1 次提交
    • 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
  12. 05 12月, 2008 1 次提交
  13. 07 8月, 2008 2 次提交