1. 22 6月, 2010 1 次提交
  2. 01 5月, 2010 1 次提交
  3. 17 4月, 2010 1 次提交
  4. 26 3月, 2010 4 次提交
  5. 10 3月, 2010 1 次提交
  6. 26 1月, 2010 2 次提交
  7. 08 10月, 2009 2 次提交
    • J
      iwlwifi: LED cleanup · e932a609
      Johannes Berg 提交于
      The iwlwifi drivers have LED blinking requirements that
      mac80211 cannot fulfill due to the use of just a single
      LED instead of different ones for TX, RX, radio etc.
      Instead, the single LED blinks according to transfers
      and is solid on the rest of the time. As such, having
      LED class devices registered that mac80211 triggers are
      connected to is pointless as we don't use the triggers
      anyway.
      
      Remove all the useless code and add hooks into the
      driver itself. At the same time, make the LED code
      abstracted so the core code that determines blink rate
      etc. can be shared between 3945 and agn in iwlcore.
      
      At the same time, the fact that we removed the use of
      the mac80211 LED triggers means we can also remove the
      IWLWIFI_LEDS Kconfig symbol since the LED support is
      now self-contained.
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      e932a609
    • J
      iwlwifi: device tracing · be1a71a1
      Johannes Berg 提交于
      In order to have an easier way to debug issues, create
      trace events (using the ftrace framework) that will
      allow us to follow exactly what the driver is doing
      with the device.
      
      The text format isn't all that useful, but the binary
      format can also be obtained easily via debugfs and
      then analysed on the fly or offline with debugging
      tools.
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      be1a71a1
  8. 11 6月, 2009 1 次提交
  9. 17 3月, 2009 2 次提交
  10. 28 2月, 2009 1 次提交
    • R
      iwlwifi: Fix and rework Kconfig file · 80bc5393
      Reinette Chatre 提交于
      Fixes:
      - iwlwifi is an optional driver and should thus not default to 'y'.
      - 3945 now depends on IWLCORE.
      
      Rework:
      - There is not a case when IWLCORE should not be selected. At the same time
        the driver does not use IWLWIFI or IWLCORE. We can just merge the usage of
        these two. With IWLWIFI being the driver name we proceed to use just it and
        replace instances of IWLCORE with it. The module name does not change
        and is still iwlcore.
      - Both IWLAGN and IWL3945 are selecting FW_LOADER, we can thus just move
        this up to one select when IWLWIFI is selected.
      - IWL5000 now supports Intel Wireless Wifi 100, 6000, and 6050 series.
      - Now that 3945 depends on IWLWIFI we can also indicate its dependency on
        MAC80211_LEDS and LEDS_CLASS at this level.
      - IWLAGN_LEDS is not used by driver - remove it.
      - IWLAGN_SPECTRUM_MEASUREMENT actually depends on IWLWIFI as it forms part
        of iwlcore module. Move this config up in Kconfig to reflect that and also
        change name to IWLWIFI_SPECTRUM_MEASUREMENT.
      - CONFIG_IWLWIFI_RFKILL is used by iwlagn as well as iwl3945, add text to
        description that indicates this.
      - CONFIG_IWL3945_RFKILL does not exist - remove usage from driver.
      - Add "iwlagn" to end of description of IWLAGN to help people understand
        what iwlagn means in rest of Kconfig text.
      - Add "iwl3945" to end of description of IWL3945 to help people understand
        what iwlagn means in rest of Kconfig text.
      - Change IWLWIFI_DEBUGFS description to indicate that only iwlagn supports
        it (for now).
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      Reported-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      80bc5393
  11. 10 2月, 2009 1 次提交
  12. 30 1月, 2009 2 次提交
  13. 05 12月, 2008 1 次提交
  14. 22 11月, 2008 1 次提交
  15. 05 8月, 2008 3 次提交
  16. 15 6月, 2008 2 次提交
  17. 15 5月, 2008 3 次提交
  18. 08 5月, 2008 3 次提交
  19. 23 4月, 2008 1 次提交
  20. 17 4月, 2008 2 次提交
  21. 02 4月, 2008 1 次提交
  22. 28 3月, 2008 1 次提交
    • M
      iwlwifi: Add led support · ab53d8af
      Mohamed Abbas 提交于
      This patch add LEDS support to 3965 and 4965 drivers. It is based on
      led trigger and class. For our drivers we needed to avoid two things.
      1- We receive led trigger on/off on each Rx\Tx frame. In our driver
          we can not call led command like that. In this driver once driver
          receive a start of traffic it call the led command to start blinking
          then we count all bytes of Tx and Rx frame, after two second we count the
          blink rate of last two second then id blink rate changed we call the led
           commands
      2- Since we can call led command very often, we make sure we call the
          led command after we receive the statistics notification so
          we don't need to wake up the ucode id it is in sleep state.
          This patch was tested with 4965 and 3945.
      Signed-off-by: NMohamed Abbas <mabbas@linux.intel.com>
      Signed-off-by: Ian Schram<ischram@telenet.be>
      Signed-off-by: NTomas Winkler <tomas.winkler@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      ab53d8af
  23. 26 3月, 2008 2 次提交
  24. 14 3月, 2008 1 次提交