1. 27 11月, 2012 1 次提交
    • E
      wlcore: start sta role on CHANGED_BSSID · 3230f35e
      Eliad Peller 提交于
      Make the connection flow simpler by starting
      sta role on bssid change.
      
      Currently, we start dev role when going idle-off,
      and start the sta role only after association
      indication. This complicates the connection
      flow with some possible intermediate states.
      
      Make it simpler by starting sta role on bssid change,
      which now happens *before* auth req get sent.
      
      Update the handling of mac80211's notifications
      and change wl1271_join/unjoin accordingly -
      * Split wl1271_join() into wlcore_join (tuning on
        a channel/bssid) and wlcore_set_assoc (configure
        sta after association).
      * Rename wl1271_unjoin() to wlcore_unset_assoc(), as
        it is no longer the inversion of wl1271_join()
        (now it's only used to disconnect associated sta /
        joined ibss, without stopping the role).
      * Set ssid before starting station role (needed for
        start_role(sta)
      
      While on it, split wl1271_bss_info_changed_sta() into
      some sub-functions.
      
      since we no longer use dev role in the connection flow,
      we now always use the hlid of the sta role.
      Signed-off-by: NEliad Peller <eliad@wizery.com>
      Reviewed-by: NArik Nemtsov <arik@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      3230f35e
  2. 27 9月, 2012 5 次提交
  3. 31 7月, 2012 2 次提交
  4. 18 7月, 2012 2 次提交
  5. 27 6月, 2012 1 次提交
    • E
      wlcore: fix broken TX due to wrong queuing of recovery · 7a50bdfb
      Eyal Shapira 提交于
      commit 14bba17b "wl12xx: Propagate errors from wl1271_raw_write32"
      breaks down TX in certain scenarios. wl1271_irq_locked() propagates
      errors from wl1271_tx_work_locked however it may return -EBUSY
      when the FW queues are full which is a legitimate case and not a
      a real error. In this case a recovery is triggered by wl1271_irq
      and this keeps repeating itself so TX is completely broken.
      Fix it by avoiding propagating return values as errors even if they
      aren't. Only bus (SDIO or SPI) ops failures would be progagated
      as only these should trigger recovery.
      Signed-off-by: NEyal Shapira <eyal@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      7a50bdfb
  6. 22 6月, 2012 3 次提交
  7. 14 6月, 2012 1 次提交
    • E
      wlcore: send EAPOLs with basic rate policy · 8f1a8684
      Eyal Shapira 提交于
      EAPOLs are sent at high rates as they are considered
      data packets. Some APs like Motorola Symbol AP7131 and AP650
      don't respond well to these rates and don't respond with
      EAPOL 3/4 consistently. When sending EAPOL 2/4 at 54Mbps
      we've seen approx 30% success rate in getting EAPOL 3/4 response
      while using 11Mbps we got 100% success.
      To increase the chances of successful 4-Way handshake with
      such APs, send EAPOLs with basic rate policy in order to avoid
      high rates.
      Signed-off-by: NEyal Shapira <eyal@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      8f1a8684
  8. 07 6月, 2012 7 次提交
  9. 05 6月, 2012 4 次提交
  10. 12 4月, 2012 13 次提交
  11. 08 3月, 2012 1 次提交