1. 11 8月, 2015 1 次提交
    • E
      wlcore: add p2p device support · 7845af35
      Eliad Peller 提交于
      When starting a p2p mgmt interface, enable its device role. This
      allows us to keep the sta role disabled and scan on the dev role.
      
      In general, p2p management interfaces cannot send vif-specific commands
      to FW, as the vif role id is invalid. Only off-channel data and scans
      happen on this vif, so most ops are not relevant.
      
      If the vif is a p2p mgmt vif, block some mac80211 ops.
      
      Configure rate policies for p2p mgmt interface, as
      otherwise p2p packets come out with arbitrary rates.
      
      Since wpa_supplicant currently doesn't support standalone
      p2p device mode (without another attached managed interface),
      add p2p device to the allowed interface combinations without
      decreasing the allowed station count.
      
      Moreover, increase the station count in some cases, as AP
      mode usually starts as station interface, and the AP interface
      is now different from the p2p management one).
      Signed-off-by: NArik Nemtsov <arik@wizery.com>
      Signed-off-by: NEliad Peller <eliad@wizery.com>
      Signed-off-by: NKalle Valo <kvalo@codeaurora.org>
      7845af35
  2. 09 1月, 2015 1 次提交
  3. 14 2月, 2014 2 次提交
  4. 23 10月, 2013 1 次提交
  5. 04 12月, 2012 1 次提交
  6. 28 11月, 2012 1 次提交
    • V
      wlcore: add new reg-domain configuration command · 6b70e7eb
      Victor Goldenshtein 提交于
      In 18xx the calibration process of the PHY Cortex domain
      requires to perform an active calibration of the channel
      before it can be used for transmission. To fulfill world
      wide regulatory restrictions, fw should be always
      synchronized/updated with current CRDA configuration.
      Add a new "CMD_DFS_CHANNEL_CONFIG" command to update the
      fw with current reg-domain, this command passes a bit map
      of channels that are allowed to be used for transmission.
      
      The driver shall update the fw during initialization and
      after each change in the current reg-domain
      configuration. The driver will save the channel number of
      incoming beacons during the scan process, as they might
      be a result of the passive scan on
      "IEEE80211_CHAN_PASSIVE_SCAN" channel and will update the
      fw accordingly once the scan is finished, the purpose of
      this is to be ready in case of the authentication request
      on one of these disabled (uncalibrated) channels.
      
      The new command requires to wait for the fw completion
      event "DFS_CHANNELS_CONFIG_COMPLETE_EVENT".
      
      No scan commands (including the sched scan) can be
      executed concurrently with the "CMD_DFS_CHANNEL_CONFIG",
      wl->mutex ensures that.
      
      [Arik - move reset of reg_ch_conf_last to safe place inside
      op_stop_locked]
      [Eliad - adjust to new event waiting api]
      Signed-off-by: NVictor Goldenshtein <victorg@ti.com>
      Signed-off-by: NArik Nemtsov <arik@wizery.com>
      Signed-off-by: NEliad Peller <eliad@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      6b70e7eb
  7. 27 11月, 2012 2 次提交
    • E
      wlcore: split 18xx and 12xx scan mechanism · 78e28062
      Eliad Peller 提交于
      The scan APIs of 12xx and 18xx are totally different.
      Use some common functions as much as possible (e.g.
      for setting scan channels), but split scan.c into
      chip-specific scan.c files, each implementing its
      own scan mechanism.
      
      (in other words - move most of the current wlcore's
      scan.c into wl12xx, and implement a similar mechanism
      in 18xx, according to the new api)
      
      New wlcore ops are introduced in order to call the
      chip-specific scan functions.
      
      The template indices used for each scan (regular/scheduled)
      are also different between the chips, so set the correct
      indices used for each scan type after identifying the chip.
      Signed-off-by: NEliad Peller <eliad@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      78e28062
    • E
      wlcore: specify correct supported_rates · 42ec1f82
      Eliad Peller 提交于
      The supported_rates field should contain all our supported
      rates, even if the remote peer doesn't support them.
      
      (rename CONF_TX_AP_ENABLED_RATES to CONF_TX_ENABLED_RATES,
      as we now use it for both ap and sta)
      Signed-off-by: NEliad Peller <eliad@wizery.com>
      Reviewed-by: NArik Nemtsov <arik@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      42ec1f82
  8. 27 9月, 2012 1 次提交
  9. 11 7月, 2012 1 次提交
  10. 21 6月, 2012 2 次提交
  11. 05 6月, 2012 1 次提交
  12. 12 4月, 2012 8 次提交
  13. 15 2月, 2012 3 次提交
  14. 15 12月, 2011 2 次提交
  15. 01 12月, 2011 1 次提交
  16. 08 11月, 2011 2 次提交
  17. 11 10月, 2011 4 次提交
  18. 07 10月, 2011 6 次提交