This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
en:users:drivers:iwlwifi [2016/01/31 22:09] Emmanuel Grumbach |
en:users:drivers:iwlwifi [2016/04/21 07:16] Emmanuel Grumbach |
||
---|---|---|---|
Line 13: | Line 13: | ||
* IBSS (Ad-Hoc) mode | * IBSS (Ad-Hoc) mode | ||
* AP mode on 2.4GHz (on devices driven by iwlmvm) | * AP mode on 2.4GHz (on devices driven by iwlmvm) | ||
- | * AP mode on 5.2GHz on 7265D and 8260 in certain conditions only | ||
* P2P (on devices driven by iwlmvm) | * P2P (on devices driven by iwlmvm) | ||
* 802.11a/b/g/n/ac (depending on the device) | * 802.11a/b/g/n/ac (depending on the device) | ||
Line 20: | Line 19: | ||
===== Supported Devices ===== | ===== Supported Devices ===== | ||
The following devices are supported (since kernel version): | The following devices are supported (since kernel version): | ||
+ | * [[http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/dual-band-wireless-ac-8265-brief.pdf|Intel® Wireless 8265]] (4.6) | ||
+ | * [[http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/dual-band-wireless-ac-3168-brief.pdf|Intel® Wireless 3168]] (4.6) | ||
* [[http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/dual-band-wireless-ac-8260-brief.pdf|Intel® Wireless 8260]] (4.1) | * [[http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/dual-band-wireless-ac-8260-brief.pdf|Intel® Wireless 8260]] (4.1) | ||
* Intel® Wireless 4165 (4.1) | * Intel® Wireless 4165 (4.1) | ||
Line 116: | Line 117: | ||
For bug reports and debugging , please see the [[en:users:drivers:iwlwifi:Debugging|page]] dedicated to that. | For bug reports and debugging , please see the [[en:users:drivers:iwlwifi:Debugging|page]] dedicated to that. | ||
+ | ===== 7260 and 7265 support ===== | ||
+ | 7260 and 7265 will not be supported by the newest firmware versions: the last firmware that was released for these devices is -17.ucode. Bug fixes will be ported to -17.ucode. Note that 7265D can run later firmware versions. In order to determine if your 7265 device is a 'D' version, you can check the dmesg output: | ||
+ | |||
+ | <code> | ||
+ | Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210 | ||
+ | </code> | ||
+ | The revision number of a 7265D device is 0x210, if you see any other number, you have a 7265 device. | ||
===== Firmware_class dependency ===== | ===== Firmware_class dependency ===== | ||
Line 139: | Line 147: | ||
If you checkout an earlier branch / commit in backport-iwlwifi.git, you might not be able to work against the most recent kernel. Please keep that in mind. | If you checkout an earlier branch / commit in backport-iwlwifi.git, you might not be able to work against the most recent kernel. Please keep that in mind. | ||
We have a release cycle based on the backport tree. These [[en:users:drivers:iwlwifi:Core_release|Core releases]] can be very useful for someone who wants to integrate our WiFi solution into his home made system. | We have a release cycle based on the backport tree. These [[en:users:drivers:iwlwifi:Core_release|Core releases]] can be very useful for someone who wants to integrate our WiFi solution into his home made system. | ||
- | |||
===== About platform noise ===== | ===== About platform noise ===== | ||
Line 152: | Line 159: | ||
* The PCIe bus, especially when switching in/out of power saving modes. | * The PCIe bus, especially when switching in/out of power saving modes. | ||
* USB3 and graphics (in certain scenarios). | * USB3 and graphics (in certain scenarios). | ||
- | * Sometimes, even the fact that several ingredients’ Ground lines are connected can cause noise. | + | * Sometimes, even the fact that several ingredients’ ground lines are connected can cause noise. |
This kind of interference might happen on 2.4GHz band, it is much less likely to happen on 5.2GHz band. | This kind of interference might happen on 2.4GHz band, it is much less likely to happen on 5.2GHz band. |