1. 07 2月, 2012 1 次提交
  2. 05 1月, 2012 1 次提交
    • S
      iwlegacy: move some i/o helpers out of inline · 17d4eca6
      Stanislaw Gruszka 提交于
      This save us about 20k of text size, and should have no impact on
      performance as hot paths do not use much I/O.
      
      Before:
         text	   data	    bss	    dec	    hex	filename
       108512	   1784	    168	 110464	  1af80	drivers/net/wireless/iwlegacy/iwl3945.ko
       165730	   2164	    156	 168050	  29072	drivers/net/wireless/iwlegacy/iwl4965.ko
        91942	    328	     48	  92318	  1689e	drivers/net/wireless/iwlegacy/iwlegacy.ko
      
      After:
         text	   data	    bss	    dec	    hex	filename
        95556	   1784	    168	  97508	  17ce4	drivers/net/wireless/iwlegacy/iwl3945.ko
       154853	   2164	    156	 157173	  265f5	drivers/net/wireless/iwlegacy/iwl4965.ko
        91634	    328	     48	  92010	  1676a	drivers/net/wireless/iwlegacy/iwlegacy.ko
      Signed-off-by: NStanislaw Gruszka <sgruszka@redhat.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      17d4eca6
  3. 07 12月, 2011 1 次提交
  4. 15 11月, 2011 32 次提交
  5. 04 10月, 2011 1 次提交
    • E
      mac80211: pass vif param to conf_tx() callback · 8a3a3c85
      Eliad Peller 提交于
      tx params should be configured per interface.
      add ieee80211_vif param to the conf_tx callback,
      and change all the drivers that use this callback.
      
      The following spatch was used:
      @rule1@
      struct ieee80211_ops ops;
      identifier conf_tx_op;
      @@
      	ops.conf_tx = conf_tx_op;
      
      @rule2@
      identifier rule1.conf_tx_op;
      identifier hw, queue, params;
      @@
      	conf_tx_op (
      -		struct ieee80211_hw *hw,
      +		struct ieee80211_hw *hw, struct ieee80211_vif *vif,
      		u16 queue,
      		const struct ieee80211_tx_queue_params *params) {...}
      Signed-off-by: NEliad Peller <eliad@wizery.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      8a3a3c85
  6. 28 9月, 2011 1 次提交
  7. 22 9月, 2011 1 次提交
    • S
      iwlegacy: do not use interruptible waits · 65d0f19e
      Stanislaw Gruszka 提交于
      iwlegacy version of fix:
      
      commit effd4d9a
      Author: Johannes Berg <johannes.berg@intel.com>
      Date:   Thu Sep 15 11:46:52 2011 -0700
      
          iwlagn: do not use interruptible waits
      
          Since the dawn of its time, iwlwifi has used
          interruptible waits to wait for synchronous
          commands and firmware loading.
      
          This leads to "interesting" bugs, because it
          can't actually handle the interruptions; for
          example when a command sending is interrupted
          it will assume the command completed fully,
          and then leave it pending, which leads to all
          kinds of trouble when the command finishes
          later.
      
          Since there's no easy way to gracefully deal
          with interruptions, fix the driver to not use
          interruptible waits.
      
          This at least fixes the error
          iwlagn 0000:02:00.0: Error: Response NULL in  'REPLY_SCAN_ABORT_CMD'
      
          I have seen in P2P testing, but it is likely
          that there are other errors caused by this.
      
      Cc: stable@kernel.org # 2.6.39+
      Signed-off-by: NStanislaw Gruszka <sgruszka@redhat.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      65d0f19e
  8. 11 6月, 2011 2 次提交
    • S
      iwlegacy: remove firmware event log · 1ba2f121
      Stanislaw Gruszka 提交于
      Messages like that
      
      iwl4965 0000:03:00.0: Start IWL Event Log Dump: display last 20 entries
      iwl4965 0000:03:00.0: EVT_LOGT:1821445332:0x00000000:1352
      iwl4965 0000:03:00.0: EVT_LOGT:1821445332:0x00000001:1353
      iwl4965 0000:03:00.0: EVT_LOGT:1821445336:0x0000000c:0357
      iwl4965 0000:03:00.0: EVT_LOGT:1821445533:0x00000107:0106
      iwl4965 0000:03:00.0: EVT_LOGT:1821445534:0x00000000:0302
      iwl4965 0000:03:00.0: EVT_LOGT:1821445574:0x000000d4:0321
      iwl4965 0000:03:00.0: EVT_LOGT:1821445575:0x00000000:1350
      iwl4965 0000:03:00.0: EVT_LOGT:1821445576:0x00000000:1351
      iwl4965 0000:03:00.0: EVT_LOGT:1821445576:0x00000000:1352
      iwl4965 0000:03:00.0: EVT_LOGT:1821445577:0x00000001:1353
      iwl4965 0000:03:00.0: EVT_LOGT:1821445581:0x0000000d:0357
      iwl4965 0000:03:00.0: EVT_LOGT:1821446327:0x00000107:0106
      iwl4965 0000:03:00.0: EVT_LOGT:1821446328:0x00000000:0302
      iwl4965 0000:03:00.0: EVT_LOGT:1821446368:0x000000d4:0321
      iwl4965 0000:03:00.0: EVT_LOGT:1821446369:0x00000000:1350
      iwl4965 0000:03:00.0: EVT_LOGT:1821446370:0x00000000:1351
      iwl4965 0000:03:00.0: EVT_LOGT:1821446370:0x00000000:1352
      iwl4965 0000:03:00.0: EVT_LOGT:1821446371:0x00000001:1353
      iwl4965 0000:03:00.0: EVT_LOGT:1821446375:0x0000000e:0357
      iwl4965 0000:03:00.0: EVT_LOGT:1821446383:0x00000000:0125
      
      are completely useless for me. Remove bunch of code that generate them.
      Signed-off-by: NStanislaw Gruszka <sgruszka@redhat.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      1ba2f121
    • S
      iwlegacy: remove reset rf infrastructure · dd6d2a8a
      Stanislaw Gruszka 提交于
      We do not reset radio anymore, hence don't need that code too.
      Signed-off-by: NStanislaw Gruszka <sgruszka@redhat.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      dd6d2a8a