20 Dec, 2008

2 commits


13 Dec, 2008

2 commits


07 Dec, 2008

1 commit


05 Dec, 2008

5 commits


26 Nov, 2008

11 commits

  • In order to be consistent with NL80211_ATTR_POWER_RULE_MAX_EIRP,
    change NL80211_FREQUENCY_ATTR_MAX_TX_POWER to use mBm and U32 instead
    of dBm and U8. This is a userspace interface change, but the previous
    version had not yet been pushed upstream and there are no userspace
    programs using this yet, so there is justification to get this change in
    as long as it goes in before the previous version gets out.

    Signed-off-by: Jouni Malinen
    Signed-off-by: John W. Linville

    Jouni Malinen
     
  • This is useful information to provide for userspace (e.g., hostapd needs
    this to generate Country IE).

    Signed-off-by: Jouni Malinen
    Signed-off-by: John W. Linville

    Jouni Malinen
     
  • This adds API to cfg80211 to allow wireless drivers to inform
    us if their firmware can handle regulatory considerations *and*
    they cannot map these regulatory domains to an ISO / IEC 3166
    alpha2. In these cases we skip the first regulatory hint instead
    of expecting the driver to build their own regulatory structure,
    providing us with an alpha2, or using the reg_notifier().

    Signed-off-by: Luis R. Rodriguez
    Acked-by: Zhu Yi
    Signed-off-by: John W. Linville

    Luis R. Rodriguez
     
  • This adds country IE parsing to mac80211 and enables its usage
    within the new regulatory infrastructure in cfg80211. We parse
    the country IEs only on management beacons for the BSSID you are
    associated to and disregard the IEs when the country and environment
    (indoor, outdoor, any) matches the already processed country IE.

    To avoid following misinformed or outdated APs we build and use
    a regulatory domain out of the intersection between what the AP
    provides us on the country IE and what CRDA is aware is allowed
    on the same country.

    A secondary device is allowed to follow only the same country IE
    as it make no sense for two devices on a system to be in two
    different countries.

    In the case the AP is using country IEs for an incorrect country
    the user may help compliance further by setting the regulatory
    domain before or after the IE is parsed and in that case another
    intersection will be performed.

    CONFIG_WIRELESS_OLD_REGULATORY is supported but requires CRDA
    present.

    Signed-off-by: Luis R. Rodriguez
    Acked-by: Johannes Berg
    Signed-off-by: John W. Linville

    Luis R. Rodriguez
     
  • Lets remain consistent and mark rds with > NL80211_MAX_SUPP_REG_RULES
    number of reg rules as invalid in is_valid_rd().

    Signed-off-by: Luis R. Rodriguez
    Acked-by: Johannes Berg
    Signed-off-by: John W. Linville

    Luis R. Rodriguez
     
  • kobject_uevent_env() can return an error but it just tells us
    if the uvent was built/sent or not, it doesn't tell us anything
    about what happened in userspace, whether the udev rule was present
    nor does it tell us if CRDA was present or not. So remove
    the informative complaint about it assuming it will tell us
    such things.

    Note that you can determine if CRDA is present after loading cfg80211
    by using:

    is_old_static_regdom(cfg80211_regdomain)

    but this doesn't account for possible user install after initial
    boot, and also for when the user uses the static EU regulatory
    domain.

    Signed-off-by: Luis R. Rodriguez
    Acked-by: Johannes Berg
    Signed-off-by: John W. Linville

    Luis R. Rodriguez
     
  • When intersecting it is possible that set_regdom() was called
    with a regulatory domain which we'll only use as an aid to
    build a final regulatory domain.

    Signed-off-by: Luis R. Rodriguez
    Acked-by: Johannes Berg
    Signed-off-by: John W. Linville

    Luis R. Rodriguez
     
  • So far the __set_regdom() code is pretty generic as the
    intersection case is fairly straight forward; this will however
    change when 802.11d support is added so lets separate intersection
    code for now in preparation for 802.11d support.

    This patch only has slight functional changes.

    Signed-off-by: Luis R. Rodriguez
    Acked-by: Johannes Berg
    Signed-off-by: John W. Linville

    Luis R. Rodriguez
     
  • We have control over the REGDOM_SET_BY_* macros passed
    so remove the switch.

    This patch has no functional changes.

    Signed-off-by: Luis R. Rodriguez
    Acked-by: Johannes Berg
    Signed-off-by: John W. Linville

    Luis R. Rodriguez
     
  • We have complete control over REGDOM_SET_BY_* enum passed
    down to __regulatory_hint() as such there is no need to
    account for unexpected REGDOM_SET_BY_*'s, lets just remove
    the switch statement as this code does not change and
    won't change even when we add 802.11d support.

    This patch has no functional changes.

    Signed-off-by: Luis R. Rodriguez
    Acked-by: Johannes Berg
    Signed-off-by: John W. Linville

    Luis R. Rodriguez
     
  • Regulatory rules with negative frequencies are now
    marked as invalid in is_valid_reg_rule().

    Signed-off-by: Luis R. Rodriguez
    Acked-by: Johannes Berg
    Signed-off-by: John W. Linville

    Luis R. Rodriguez
     

22 Nov, 2008

3 commits


11 Nov, 2008

8 commits


01 Nov, 2008

8 commits