An error occurred fetching the project authors.
- 12 Apr, 2012 1 commit
-
-
Johannes Berg authored
The hw_params are mostly values that are derived from the actual hardware config. As such, while it is possible that MVM will require similar ones, it makes more sense -- at least for now -- to put them into the DVM struct. Signed-off-by:
Johannes Berg <johannes.berg@intel.com> Signed-off-by:
Wey-Yi Guy <wey-yi.w.guy@intel.com> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
- 08 Mar, 2012 1 commit
-
-
Johannes Berg authored
There's no need to carry around the function pointer when a boolean indicating that the EEPROM stores enhanced TX power information is sufficient. Signed-off-by:
-
- 07 Mar, 2012 1 commit
-
-
Johannes Berg authored
It's only needed in a few places. Signed-off-by:
-
- 06 Mar, 2012 3 commits
-
-
Johannes Berg authored
Writing to the global config structures is always wrong. To protect against such mistakes in the future, mark them const. Signed-off-by:
-
Johannes Berg authored
It's not really a good idea to write to the global static configuration. Use the valid TX/RX antenna information only from the HW params struct except in the case where the values from the config are used to override the values from the EEPROM. Signed-off-by:
-
Johannes Berg authored
There's no SKU override, we always just use it from EEPROM. As such, we can remove it from the config and use it in hw_param only. Since iwl_eeprom_check_sku() really needs to fill it in also rename that to iwl_eeprom_init_hw_params(). Signed-off-by:
-
- 27 Feb, 2012 2 commits
-
-
Emmanuel Grumbach authored
This is temporary, but at least we can now throw the bus away and move the iwl_pci_{probe,remove} functions. Signed-off-by:Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by:
-
Emmanuel Grumbach authored
They don't need to be in iwl-dev.h Signed-off-by:
-
- 02 Feb, 2012 2 commits
-
-
Emmanuel Grumbach authored
From now on, the transport layer in charge of providing access to the device. So change all the driver to give a pointer to the transport to all the low level functions that actually access the device. Signed-off-by:
-
Emmanuel Grumbach authored
There is no link between the two. Ensure that the NIC is on outside the code of the EEPROM handling. Signed-off-by:
-
- 24 Jan, 2012 1 commit
-
-
Wey-Yi Guy authored
Update Copyright to 2012 Signed-off-by:
-
- 06 Jan, 2012 1 commit
-
-
Wey-Yi Guy authored
Update Copyright to 2012 Signed-off-by:
-
- 16 Dec, 2011 1 commit
-
-
Don Fry authored
Move the configuration pointer from the upper level iwl_priv to the lower level iwl_shared structure, with associated code fixes. Signed-off-by:
Don Fry <donald.h.fry@intel.com> Signed-off-by:
-
- 08 Dec, 2011 1 commit
-
-
Don Fry authored
The eeprom image is a device level component, move from iwl_priv to iwl_shared, with associated code changes. Signed-off-by:
-
- 11 Nov, 2011 2 commits
-
-
Don Fry authored
The nvm_device_type is eeprom related and does not need to be part of the iwl_priv structure. Move it and eliminate access to the iwl_priv structure. Signed-off-by:
-
Don Fry authored
Make the eeprom routines less dependent on the iwl_priv structure. Don't use the priv when bus structure is sufficient. Signed-off-by:
-
- 27 Sep, 2011 1 commit
-
-
Emmanuel Grumbach authored
As everybody knows kcalloc checks the multiplication is safe and that we don't run into overflow. Signed-off-by:
-
- 19 Sep, 2011 1 commit
-
-
Wey-Yi Guy authored
After driver split and no need to support legacy devices, there is no reason we need to separate the NVM access into different files, merge those. Signed-off-by:
-
- 29 Aug, 2011 2 commits
-
-
Emmanuel Grumbach authored
Which means that iwl-io.c doesn't need to include iwl-dev.h any more. Signed-off-by:
-
Wey-Yi Guy authored
There are number of functions with "iwlcore_" prefix which not feels right, rename those to "iwl_". No functional changes by making the renames. Signed-off-by:
-
- 16 Jul, 2011 1 commit
-
-
Wey-Yi Guy authored
After driver split, no need to make the code so complex Signed-off-by:
-
- 11 Jul, 2011 2 commits
-
-
Fry, Donald H authored
Not needed since the driver split. Eliminate redundant routine. Signed-off-by:
-
Fry, Donald H authored
Not needed since the driver split. Signed-off-by:
-
- 18 Jun, 2011 1 commit
-
-
Wey-Yi Guy authored
Same operation needed by multiple devices, move to single function. Signed-off-by:
-
- 13 May, 2011 1 commit
-
-
Johannes Berg authored
gcc is warning that a few variables in rate scaling are set but never otherwise used. This pointed out a few simplifications. Signed-off-by:
-
- 30 Apr, 2011 1 commit
-
-
Don Fry authored
All agn devices use the same eeprom semaphore and calib version routines. Delete the indirection and move the semaphore routines to where they are used and make static. Signed-off-by:
-
- 29 Apr, 2011 1 commit
-
-
Stanislaw Gruszka authored
Since commit f844a709 Author: Stanislaw Gruszka <sgruszka@redhat.com> Date: Fri Jan 28 16:47:44 2011 +0100 iwlwifi: do not set tx power when channel is changing we set device tx power during initialization to priv->tx_power_next, which itself is initialized to minimum power. That changed default behaviour of driver. Previously we initialized device to transmit at maximum available power by default. Patch change again to previous behaviour and cleanup tx power initialization. Fortunately this is not critical fix, as mac80211 layer setup tx power lately to 14dB, hence device does not operate at minimal transmit power all the time. Signed-off-by:
Stanislaw Gruszka <sgruszka@redhat.com> Signed-off-by:
-
- 18 Apr, 2011 1 commit
-
-
Johannes Berg authored
There are a number of things in the driver that may result in a BUG(), which is suboptimal since it's hard to get debugging information out of the driver in that case and the user experience is also not good :-) Almost all BUG_ON instances can be converted to WARN_ON with a few lines of appropriate error handling, so do that instead. Signed-off-by:
-
- 07 Apr, 2011 3 commits
-
-
Johannes Berg authored
This generates a massive reduction in module size: with debug: text data bss dec hex filename 670300 13136 420 683856 a6f50 iwlagn.ko (before) 388347 13136 408 401891 621e3 iwlagn.ko (after) without debug: text data bss dec hex filename 528575 13072 420 542067 84573 iwlagn.ko (before) 294192 13072 408 307672 4b1d8 iwlagn.ko (after) This also removes all the IO debug functionality since it can easily be replaced by tracing, and makes the code unnecessarily complex. I haven't done any CPU utilisation measurements, but given that the hotpaths don't use much IO it is not likely to have a negative impact; in fact, the size reduction will reduce cache pressure which possibly improves performance. Finally, an unused function or two were removed. Signed-off-by:
-
Johannes Berg authored
The hw_rev variable is used only during init, so there's no need to keep it around. Signed-off-by:
-
Wey-Yi Guy authored
Signed-off-by:
-
- 25 Mar, 2011 1 commit
-
-
Wey-Yi Guy authored
After driver split, remove the unused reference to 3945 and 4965 Signed-off-by:
-
- 21 Feb, 2011 3 commits
-
-
Wey-Yi Guy authored
Intel WiFi devices 3945 and 4965 now have their own driver in the folder drivers/net/wireless/iwlegacy Add support to build these drivers independently of the driver for AGN devices. Selecting the 3945 builds iwl3945.ko and iwl_legacy.ko, and selecting the 4965 builds iwl4965.ko and iwl_legacy.ko. iwl-legacy.ko contains code shared between both devices. The 3945 is an ABG/BG device, with no support for 802.11n. The 4965 is a 2x3 ABGN device. Signed-off-by:
Meenakshi Venkataraman <meenakshi.venkataraman@intel.com> Acked-by:
-
Wey-Yi Guy authored
This reverts commit aa833c4b.
-
Wey-Yi Guy authored
Intel WiFi devices 3945 and 4965 now have their own driver in the folder drivers/net/wireless/iwlegacy Add support to build these drivers independently of the driver for AGN devices. Selecting the 3945 builds iwl3945.ko and iwl_legacy.ko, and selecting the 4965 builds iwl4965.ko and iwl_legacy.ko. iwl-legacy.ko contains code shared between both devices. The 3945 is an ABG/BG device, with no support for 802.11n. The 4965 is a 2x3 ABGN device. Signed-off-by:
-
- 13 Dec, 2010 1 commit
-
-
Wey-Yi Guy authored
For logging EEPROM related info, instead of using IWL_DEBUG_INFO, use the dedicated logging (IWL_DEBUG_EEPROM) for easier debugging Signed-off-by:
-
- 14 Oct, 2010 1 commit
-
-
Wey-Yi Guy authored
Some of the functions in iwl-eeprom.c file are for agn devices only, Those functions do not have to be part of iwlcore.ko, so move those to iwl-agn-eeprom.c file. Signed-off-by:
-
- 07 Oct, 2010 2 commits
-
-
Johannes Berg authored
Since all devices share the same operation here, there's no need to call it indirectly. Signed-off-by:
-
Johannes Berg authored
All drivers share the same implementation, so there's no need to call this via a function pointer nor to export it. Signed-off-by:
-
- 06 Oct, 2010 1 commit
-
-
Wey-Yi Guy authored
move paramater definitions to a device paramater structure only leaving the device name, which antennas are used and what firmware file to use in the iwl_cfg structure. this will not completely remove the redundancies but greatly reduce them for devices that only vary by name or antennas. the parameters that are more likely to change within a given device family are left in iwl_cfg. also separate bt param structure added to help reduce more. Signed-off-by:
Jay Sternberg <jay.e.sternberg@intel.com> Signed-off-by:
-
