1. 17 3月, 2009 2 次提交
  2. 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
  3. 30 1月, 2009 3 次提交
  4. 01 11月, 2008 1 次提交
  5. 05 8月, 2008 1 次提交
  6. 08 7月, 2008 1 次提交
    • A
      iwlwifi: remove input device and fix rfkill state · 80fcc9e2
      Adel Gadllah 提交于
      This patch fixes the iwlwifi rfkill. It removes the input device from iwl3945,
      adds support for RFKILL_STATE_HARD_BLOCKED and calls rfkill_force_state() to
      update the state rather than accessing it directly.
      The calls to iwl|iwl3945_rfkill_set_hw_state() had to be moved because
      rfkill_force_state() cannot be called from an atomic context.
      Tested on iwl3945 and seems to work fine.
      
      Cc: Randy Dunlap <randy.dunlap@oracle.com>
      Cc: Ivo van Doorn <ivdoorn@gmail.com>
      Cc: Fabien Crespel <fcrespel@gmail.com>
      Cc: Zhu Yi <yi.zhu@intel.com>
      Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
      Signed-off-by: NAdel Gadllah <adel.gadllah@gmail.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      80fcc9e2
  7. 01 7月, 2008 1 次提交
  8. 27 6月, 2008 1 次提交
    • R
      iwlwifi: fix build for CONFIG_INPUT=n · b973e42e
      Randy Dunlap 提交于
      Fix iwlwifi so that it builds cleanly with CONFIG_INPUT=n.
      Also free the input device on exit.
      
      drivers/built-in.o: In function `iwl_rfkill_unregister':
      (.text+0xbf430): undefined reference to `input_unregister_device'
      drivers/built-in.o: In function `iwl_rfkill_init':
      (.text+0xbf51c): undefined reference to `input_allocate_device'
      drivers/built-in.o: In function `iwl_rfkill_init':
      (.text+0xbf5bf): undefined reference to `input_register_device'
      drivers/built-in.o: In function `iwl_rfkill_init':
      (.text+0xbf5e9): undefined reference to `input_free_device'
      net/built-in.o: In function `rfkill_disconnect':
      rfkill-input.c:(.text+0xe71e1): undefined reference to `input_close_device'
      rfkill-input.c:(.text+0xe71e9): undefined reference to `input_unregister_handle'
      net/built-in.o: In function `rfkill_connect':
      rfkill-input.c:(.text+0xe723e): undefined reference to `input_register_handle'
      rfkill-input.c:(.text+0xe724d): undefined reference to `input_open_device'
      rfkill-input.c:(.text+0xe725c): undefined reference to `input_unregister_handle'
      net/built-in.o: In function `rfkill_handler_init':
      rfkill-input.c:(.init.text+0x36ec): undefined reference to `input_register_handler'
      net/built-in.o: In function `rfkill_handler_exit':
      rfkill-input.c:(.exit.text+0x112c): undefined reference to `input_unregister_handler'
      make[1]: *** [.tmp_vmlinux1] Error 1
      Signed-off-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      b973e42e
  9. 15 6月, 2008 2 次提交
  10. 15 5月, 2008 1 次提交
  11. 08 5月, 2008 3 次提交
  12. 06 5月, 2008 1 次提交
  13. 30 4月, 2008 1 次提交
    • A
      iwlwifi: move the selects to the tristate drivers · 3a8209d1
      Adrian Bunk 提交于
      This patch moves the following select's:
      - RFKILL        : IWLWIFI_RFKILL -> IWLCORE
      - RFKILL_INPUT  : IWLWIFI_RFKILL -> IWLCORE
      - MAC80211_LEDS : IWL4965_LEDS   -> IWLCORE
      - LEDS_CLASS    : IWL4965_LEDS   -> IWLCORE
      - MAC80211_LEDS : IWL3945_LEDS   -> IWL3945
      - LEDS_CLASS    : IWL3945_LEDS   -> IWL3945
      
      The effects are:
      - with IWLCORE=m and/or IWL3945=m RFKILL/RFKILL_INPUT/MAC80211_LEDS/LEDS_CLASS
        are no longer wrongly forced to y
      - fixes a build error with IWLCORE=y, IWL4965=m
        might be a bug in kconfig causing it, but doing this change that is 
        anyway the right thing fixes it
      Reported-by: NCarlos R. Mafra <crmafra2@gmail.com>
      Signed-off-by: NAdrian Bunk <bunk@kernel.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      3a8209d1
  14. 28 4月, 2008 1 次提交
  15. 23 4月, 2008 1 次提交
  16. 17 4月, 2008 1 次提交
  17. 09 4月, 2008 1 次提交
  18. 08 4月, 2008 1 次提交
  19. 02 4月, 2008 1 次提交
  20. 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
  21. 26 3月, 2008 2 次提交
  22. 25 3月, 2008 1 次提交
  23. 08 3月, 2008 1 次提交
  24. 01 3月, 2008 2 次提交
  25. 29 1月, 2008 5 次提交
  26. 31 10月, 2007 1 次提交
  27. 11 10月, 2007 1 次提交