14 Jan, 2016

2 commits

  • The rule definitions here aren't really valid, they would
    be rejected if it came from userspace due to the bandwidth
    specified being bigger than the rule's width.

    This is fairly much inconsequential since the other rules
    around them do enable the bandwidth, but express that better
    using the NL80211_RRF_AUTO_BW flag.

    Signed-off-by: Johannes Berg

    Johannes Berg
     
  • cfg80211 module prints a lot of messages like below. Actually printing
    once is acceptable but sometimes it will print again and again, it looks
    very annoying. It is better to change these detail messages to debugging
    only.

    cfg80211: World regulatory domain updated:
    cfg80211: DFS Master region: unset
    cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
    cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
    cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
    cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
    cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
    cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
    cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)

    The changes in this patch is to replace pr_info with pr_debug in function
    print_rd_rules and print_regdomain_info

    Signed-off-by: Dave Young
    [change some pr_err() statements to at least keep the alpha2]
    Signed-off-by: Johannes Berg

    Dave Young
     

18 Dec, 2015

1 commit


15 Dec, 2015

3 commits


04 Dec, 2015

11 commits


03 Nov, 2015

2 commits

  • Currently, cfg80211 rejects updates of AID and listen interval parameters
    for existing entries. This information is known only at association stage
    and as a result it's impossible to update entries that were added
    unassociated.
    Fix this by allowing updates of these properies for stations that the
    driver (or mac80211) assigned unassociated state.

    This then fixes mac80211's use of NL80211_FEATURE_FULL_AP_CLIENT_STATE.

    Signed-off-by: Ayala Beker
    Signed-off-by: Emmanuel Grumbach
    Signed-off-by: Johannes Berg

    Ayala Beker
     
  • If parse_acl_data succeeds but the subsequent parsing of smps
    attributes fails, there will be a memory leak due to early returns.
    Fix that by moving the ACL parsing later.

    Cc: stable@vger.kernel.org
    Fixes: 18998c381b19b ("cfg80211: allow requesting SMPS mode on ap start")
    Signed-off-by: Ola Olsson
    Signed-off-by: Johannes Berg

    Ola Olsson
     

16 Oct, 2015

7 commits


15 Oct, 2015

6 commits


13 Oct, 2015

2 commits

  • Add the option to configure multiple 'scan plans' for scheduled scan.
    Each 'scan plan' defines the number of scan cycles and the interval
    between scans. The scan plans are executed in the order they were
    configured. The last scan plan will always run infinitely and thus
    defines only the interval between scans.
    The maximum number of scan plans supported by the device and the
    maximum number of iterations in a single scan plan are advertised
    to userspace so it can configure the scan plans appropriately.

    When scheduled scan results are received there is no way to know which
    scan plan is being currently executed, so there is no way to know when
    the next scan iteration will start. This is not a problem, however.
    The scan start timestamp is only used for flushing old scan results,
    and there is no difference between flushing all results received until
    the end of the previous iteration or the start of the current one,
    since no results will be received in between.

    Signed-off-by: Avraham Stern
    Signed-off-by: Luca Coelho
    Signed-off-by: Johannes Berg

    Avraham Stern
     
  • For location and connectivity services, userspace would often like
    to know the time when the BSS was last seen. The current "last seen"
    value is calculated in a way that makes it less useful, especially
    if the system suspended in the meantime.

    Add the ability for the driver to report a real CLOCK_BOOTTIME stamp
    that can then be reported to userspace (if present).

    Drivers wishing to use this must be converted to the new API to call
    cfg80211_inform_bss_data() or cfg80211_inform_bss_frame_data(). They
    need to ensure the reported value is accurate enough even when the
    frame might have been buffered in the device (e.g. firmware.)

    Signed-off-by: Dmitry Shmidt
    [modified to use struct, inlines]
    Signed-off-by: Johannes Berg

    Dmitry Shmidt
     

07 Oct, 2015

1 commit

  • …inux/kernel/git/jberg/mac80211-next

    Johannes Berg says:

    ====================
    For the current cycle, we have the following right now:
    * many internal fixes, API improvements, cleanups, etc.
    * full AP client state tracking in cfg80211/mac80211 from Ayala
    * VHT support (in mac80211) for mesh
    * some A-MSDU in A-MPDU support from Emmanuel
    * show current TX power to userspace (from Rafał)
    * support for netlink dump in vendor commands (myself)
    ====================

    Signed-off-by: David S. Miller <davem@davemloft.net>

    David S. Miller
     

29 Sep, 2015

2 commits

  • Currently, cfg80211 rejects capability updates for existing entries
    and as a result it's impossible to update entries that were added
    unassociated, but that is necessary to go through the full station
    states from userspace, adding a station before authentication etc.

    Fix this by allowing updates to capabilities for stations that the
    driver (or mac80211) assigned unassociated state. Drivers setting
    the full station state support flag must use the new station type
    for proper operation.

    Signed-off-by: Ayala Beker
    Signed-off-by: Luca Coelho
    Signed-off-by: Johannes Berg

    Ayala Beker
     
  • Now, PM core supports asynchronous suspend/resume mode for devices
    during system suspend/resume, and the power state transition of one
    device may be completed in separate kernel thread. PM core ensures
    all power state transition timing dependency between devices. This
    patch enables wiphy device to suspend/resume asynchronously. This can
    take advantage of multicore and improve system suspend/resume speed.

    Signed-off-by: Zhonghui Fu
    Signed-off-by: Johannes Berg

    Fu, Zhonghui
     

22 Sep, 2015

3 commits