1. 01 Jul, 2011 1 commit
  2. 24 Jun, 2011 1 commit
  3. 18 Jun, 2011 4 commits
  4. 11 Jun, 2011 3 commits
  5. 31 May, 2011 1 commit
  6. 13 May, 2011 3 commits
  7. 06 May, 2011 2 commits
    • Johannes Berg's avatar
      iwlagn: remove bytecount indirection · 94b00658
      Johannes Berg authored
      
      
      All AGN devices need the bytecount table, so
      remove the indirection and make the functions
      static again.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: default avatarWey-Yi Guy <wey-yi.w.guy@intel.com>
      94b00658
    • Cindy H. Kao's avatar
      iwlwifi: support the svtool messages interactions through nl80211 test mode · 4613e72d
      Cindy H. Kao authored
      
      
      This patch adds the feature to support the test mode operation through
      the generic netlink channel NL80211_CMD_TESTMODE between intel
      wireless device iwlwifi and the user space application svtool.
      
      The main purpose is to create a transportation layer between the iwlwifi
      device and the user space application so that the interaction between the
      user space application svtool and the iwlwifi device in the kernel space is
      in a way of generic netlink messaging.
      
      The detail specific functions are:
      
      1. The function iwl_testmode_cmd() is added to digest the svtool test command
         from the user space application. The svtool test commands are categorized  to
         three types : commands to be processed by the device ucode, commands to access
         the registers, and commands to be processed at the driver level(such as reload
         the ucode). iwl_testmode_cmd() dispatches the commands the corresponding handlers
         and reply to user space regarding the command execution status. Extra data is
         returned to the user space application if there's any.
      
      2. The function iwl_testmode_ucode_rx_pkt() is added to multicast all the spontaneous
         messages from the iwlwifi device to the user space. Regardless the message types,
         whenever there is a valid spontaneous message received by the iwlwifi ISR,
         iwl_testmode_ucode_rx_pkt() is invoked to multicast the message content to user
         space. The message content is not attacked and the message parsing is left to
         the user space application.
      
      Implementation guidelines:
      
      1. The generic netlink messaging for iwliwif test mode is through  NL80211_CMD_TESTMODE
         channel, therefore, the codes need to follow the regulations set by cfg80211.ko
         to get the actual device instance ieee80211_ops via cfg80211.ko, so that the iwlwifi
         device is indicated with ieee80211_ops and can be actually accessed.
      
         Therefore, a callback iwl_testmode_cmd() is added to the structure
         iwlagn_hw_ops in iwl-agn.c.
      
      2. It intends to utilize those low level device access APIs from iwlwifi device driver
         (ie. iwlagn.ko) rather than creating it's own set of device access functions.
         For example, iwl_send_cmd(), iwl_read32(), iwl_write8(), and iwl_write32() are reused.
      
      3. The main functions are maintained in new files instead of spreading all over the
         existing iwlwifi driver files.
      
         The new files added are :
      
         drivers/net/wireless/iwlwifi/iwl-sv-open.c
              - to handle the user space test mode application command
                and reply the respective command status to the user space application.
              - to multicast the spontaneous messages from device to user space.
      
         drivers/net/wireless/iwlwifi/iwl-testmode.h
              - the commonly referenced definitions for the TLVs used in
                the generic netlink messages
      Signed-off-by: default avatarCindy H. Kao <cindy.h.kao@intel.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: default avatarWey-Yi Guy <wey-yi.w.guy@intel.com>
      4613e72d
  8. 30 Apr, 2011 3 commits
  9. 22 Apr, 2011 6 commits
  10. 08 Apr, 2011 2 commits
  11. 07 Apr, 2011 4 commits
  12. 25 Mar, 2011 3 commits
  13. 04 Mar, 2011 1 commit
  14. 28 Feb, 2011 1 commit
  15. 25 Feb, 2011 1 commit
    • Johannes Berg's avatar
      mac80211: make tx() operation return void · 7bb45683
      Johannes Berg authored
      
      
      The return value of the tx operation is commonly
      misused by drivers, leading to errors. All drivers
      will drop frames if they fail to TX the frame, and
      they must also properly manage the queues (if they
      didn't, mac80211 would already warn).
      
      Removing the ability for drivers to return a BUSY
      value also allows significant cleanups of the TX
      TX handling code in mac80211.
      
      Note that this also fixes a bug in ath9k_htc, the
      old "return -1" there was wrong.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      Tested-by: Sedat Dilek <sedat.dilek@googlemail.com> [ath5k]
      Acked-by: Gertjan van Wingerde <gwingerde@gmail.com> [rt2x00]
      Acked-by: Larry Finger <Larry.Finger@lwfinger.net> [b43, rtl8187, rtlwifi]
      Acked-by: Luciano Coelho <coelho@ti.com> [wl12xx]
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      7bb45683
  16. 21 Jan, 2011 3 commits
  17. 19 Jan, 2011 1 commit
    • Johannes Berg's avatar
      mac80211: track receiver's aggregation reorder buffer size · 0b01f030
      Johannes Berg authored
      
      
      The aggregation code currently doesn't implement the
      buffer size negotiation. It will always request a max
      buffer size (which is fine, if a little pointless, as
      the mac80211 code doesn't know and might just use 0
      instead), but if the peer requests a smaller size it
      isn't possible to honour this request.
      
      In order to fix this, look at the buffer size in the
      addBA response frame, keep track of it and pass it to
      the driver in the ampdu_action callback when called
      with the IEEE80211_AMPDU_TX_OPERATIONAL action. That
      way the driver can limit the number of subframes in
      aggregates appropriately.
      
      Note that this doesn't fix any drivers apart from the
      addition of the new argument -- they all need to be
      updated separately to use this variable!
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      0b01f030