An error occurred fetching the project authors.
  1. 15 Jul, 2014 1 commit
  2. 25 Jun, 2014 1 commit
  3. 13 Feb, 2014 4 commits
  4. 25 Nov, 2013 1 commit
    • Luis R. Rodriguez's avatar
      cfg80211: consolidate passive-scan and no-ibss flags · 8fe02e16
      Luis R. Rodriguez authored
      These two flags are used for the same purpose, just
      combine them into a no-ir flag to annotate no initiating
      radiation is allowed.
      
      Old userspace sending either flag will have it treated as
      the no-ir flag. To be considerate to older userspace we
      also send both the no-ir flag and the old no-ibss flags.
      Newer userspace will have to be aware of older kernels.
      
      Update all places in the tree using these flags with the
      following semantic patch:
      
      @@
      @@
      -NL80211_RRF_PASSIVE_SCAN
      +NL80211_RRF_NO_IR
      @@
      @@
      -NL80211_RRF_NO_IBSS
      +NL80211_RRF_NO_IR
      @@
      @@
      -IEEE80211_CHAN_PASSIVE_SCAN
      +IEEE80211_CHAN_NO_IR
      @@
      @@
      -IEEE80211_CHAN_NO_IBSS
      +IEEE80211_CHAN_NO_IR
      @@
      @@
      -NL80211_RRF_NO_IR | NL80211_RRF_NO_IR
      +NL80211_RRF_NO_IR
      @@
      @@
      -IEEE80211_CHAN_NO_IR | IEEE80211_CHAN_NO_IR
      +IEEE80211_CHAN_NO_IR
      @@
      @@
      -(NL80211_RRF_NO_IR)
      +NL80211_RRF_NO_IR
      @@
      @@
      -(IEEE80211_CHAN_NO_IR)
      +IEEE80211_CHAN_NO_IR
      
      Along with some hand-optimisations in documentation, to
      remove duplicates and to fix some indentation.
      Signed-off-by: default avatarLuis R. Rodriguez <mcgrof@do-not-panic.com>
      [do all the driver updates in one go]
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      8fe02e16
  5. 23 Oct, 2013 2 commits
  6. 30 Sep, 2013 2 commits
  7. 25 Mar, 2013 2 commits
    • Arik Nemtsov's avatar
      wlcore: AP-mode - recover security seq num for stations · 0e752df6
      Arik Nemtsov authored
      Save the sequence number of the broadcast AP link in the wlvif. For each
      connected station, save the sequence number in the drv_priv part of
      ieee80211_sta. Use the saved numbers on recovery/resume, with the
      obligatory increment on recovery.
      Signed-off-by: default avatarArik Nemtsov <arik@wizery.com>
      Signed-off-by: default avatarLuciano Coelho <coelho@ti.com>
      0e752df6
    • Arik Nemtsov's avatar
      wlcore: consolidate tx_seq handling on recovery · 93d5d100
      Arik Nemtsov authored
      Accumulate the total number of sent packets per-link to find out how far
      the encryption sequence number has progressed. Use this number as the
      initial security sequence number after recovery.
      
      This consolidates security sequence handling for both chip families, as
      we no longer have to rely on 12xx specific Tx completion.
      
      A fortunate side effect of this is correct management of seq numbers for
      AP roles and multi-role scenarios.
      
      When a link is removed we save the last seq number on a persistent part
      of the wlvif. This helps the data survive through recoveries/suspends,
      which also entail changes in the hlid of the link.
      
      This functionality is STA only currently.
      Signed-off-by: default avatarArik Nemtsov <arik@wizery.com>
      Signed-off-by: default avatarLuciano Coelho <coelho@ti.com>
      93d5d100
  8. 08 Feb, 2013 1 commit
    • Luciano Coelho's avatar
      wlcore: fix wrong remote rates when starting STA role · 9c3a8d99
      Luciano Coelho authored
      In wl18xx, we use a new ACX command in order to set the remote
      supported rates, once we know it (ie. after association).  The wl12xx
      firmware doesn't support changing the rates after the STA is started,
      so we need to use all supported rates.
      
      Commit 530abe19 (wlcore: add ACX_PEER_CAP command) broke that by using
      wlvif->rate_set when starting the STA role.
      Signed-off-by: default avatarLuciano Coelho <coelho@ti.com>
      9c3a8d99
  9. 11 Dec, 2012 2 commits
  10. 05 Dec, 2012 3 commits
  11. 04 Dec, 2012 2 commits
  12. 30 Nov, 2012 1 commit
  13. 28 Nov, 2012 2 commits
    • Arik Nemtsov's avatar
      wlcore: use new set bandwidth command to adjusting channel BW · 5f9b6777
      Arik Nemtsov authored
      We support changing the channel BW when we started the STA role on
      a 40Mhz bandwidth. Otherwise a reconnection is required.
      Save the started channel width and use it when channel width updates
      arrive.
      Signed-off-by: default avatarArik Nemtsov <arik@wizery.com>
      Signed-off-by: default avatarLuciano Coelho <coelho@ti.com>
      5f9b6777
    • Victor Goldenshtein's avatar
      wlcore: add new reg-domain configuration command · 6b70e7eb
      Victor Goldenshtein authored
      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: default avatarVictor Goldenshtein <victorg@ti.com>
      Signed-off-by: default avatarArik Nemtsov <arik@wizery.com>
      Signed-off-by: default avatarEliad Peller <eliad@wizery.com>
      Signed-off-by: default avatarLuciano Coelho <coelho@ti.com>
      6b70e7eb
  14. 27 Nov, 2012 8 commits
  15. 27 Sep, 2012 3 commits
  16. 18 Jul, 2012 1 commit
    • Luciano Coelho's avatar
      wlcore: wait for command completion event when sending CMD_ROLE_STOP · 5285eb54
      Luciano Coelho authored
      We need to wait for the command completion event when we send the
      CMD_ROLE_STOP event otherwise we may try to send CMD_ROLE_START too
      soon and get out-of-sync with the firmware.
      
      In some cases, the firmware may not send the event, so we wait for the
      event or for the timeout, whichever comes first.
      
      This patch is based on an earlier version by Eliad.
      
      Cc: Eliad Peller <eliad@wizery.com>
      Signed-off-by: default avatarLuciano Coelho <coelho@ti.com>
      5285eb54
  17. 10 Jul, 2012 2 commits
    • Yoni Divinsky's avatar
      wlcore: change the wait for event mechanism · c45ee4ff
      Yoni Divinsky authored
      wlcore needs to wait for certain events for example
      for roc complete event. Usually the events are received
      from the FW very fast, therefore wlcore can poll with
      a short delay and if after a second the event was
      not received yet poll with a long (1-5 msec) delay.
      
      This implementation is similar to the sending of
      commands to the FW.
      
      Empirically the change reduced the wait for roc event
      from ~10-40msec to 100s of usecs.
      
      [replace udelay/msleep with usleep_range - Arik]
      Signed-off-by: default avatarYoni Divinsky <yoni.divinsky@ti.com>
      Signed-off-by: default avatarArik Nemtsov <arik@wizery.com>
      c45ee4ff
    • Yoni Divinsky's avatar
      wlcore: add probe request templates for sched and one-shot scans · 3df74f46
      Yoni Divinsky authored
      The driver configures the firmware template for probe requests during
      the scan process.  If the same template is used for one-shot and sched
      scans they will override each other when running scans simultaneously.
      
      This fix works only on firmwares later than X.3.9.2.112 for single
      role and X.3.9.2.23 for multi-role.
      
      [Some cleaning-up and renaming of the quirk to something smaller --
      Luca.]
      Signed-off-by: default avatarYoni Divinsky <yoni.divinsky@ti.com>
      Signed-off-by: default avatarLuciano Coelho <coelho@ti.com>
      3df74f46
  18. 26 Jun, 2012 2 commits