<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux.git/drivers/net/wireless/ath, branch v2.6.36</title>
<subtitle>Linux kernel source tree</subtitle>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/'/>
<entry>
<title>ath9k_hw: fix regression in ANI listen time calculation</title>
<updated>2010-10-06T19:58:28+00:00</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@openwrt.org</email>
</author>
<published>2010-10-03T17:07:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=918df629d6a558ab9eb53350493f618812239a4c'/>
<id>918df629d6a558ab9eb53350493f618812239a4c</id>
<content type='text'>
  wireless-testing
  commit 37e5bf6535a4d697fb9fa6f268a8354a612cbc00
  Author: Luis R. Rodriguez &lt;lrodriguez@atheros.com&gt;
  Date:   Sat Jun 12 00:33:40 2010 -0400

    ath9k_hw: fix clock rate calculations for ANI

This commit accidentally broke clock rate calculation by doubling the
calculated clock rate

Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  wireless-testing
  commit 37e5bf6535a4d697fb9fa6f268a8354a612cbc00
  Author: Luis R. Rodriguez &lt;lrodriguez@atheros.com&gt;
  Date:   Sat Jun 12 00:33:40 2010 -0400

    ath9k_hw: fix clock rate calculations for ANI

This commit accidentally broke clock rate calculation by doubling the
calculated clock rate

Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath9k_hw: fix parsing of HT40 5 GHz CTLs</title>
<updated>2010-08-31T18:52:23+00:00</updated>
<author>
<name>Luis R. Rodriguez</name>
<email>lrodriguez@atheros.com</email>
</author>
<published>2010-08-30T23:26:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=904879748d7439a6dabdc6be9aad983e216b027d'/>
<id>904879748d7439a6dabdc6be9aad983e216b027d</id>
<content type='text'>
The 5 GHz CTL indexes were not being read for all hardware
devices due to the masking out through the CTL_MODE_M mask
being one bit too short. Without this the calibrated regulatory
maximum values were not being picked up when devices operate
on 5 GHz in HT40 mode. The final output power used for Atheros
devices is the minimum between the calibrated CTL values and
what CRDA provides.

Cc: stable@kernel.org [2.6.27+]
Signed-off-by: Luis R. Rodriguez &lt;lrodriguez@atheros.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The 5 GHz CTL indexes were not being read for all hardware
devices due to the masking out through the CTL_MODE_M mask
being one bit too short. Without this the calibrated regulatory
maximum values were not being picked up when devices operate
on 5 GHz in HT40 mode. The final output power used for Atheros
devices is the minimum between the calibrated CTL values and
what CRDA provides.

Cc: stable@kernel.org [2.6.27+]
Signed-off-by: Luis R. Rodriguez &lt;lrodriguez@atheros.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath9k_hw: Fix EEPROM uncompress block reading on AR9003</title>
<updated>2010-08-31T18:52:23+00:00</updated>
<author>
<name>Luis R. Rodriguez</name>
<email>lrodriguez@atheros.com</email>
</author>
<published>2010-08-30T23:26:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=803288e61e346ba367373bc7d5eeb6e11c81a33c'/>
<id>803288e61e346ba367373bc7d5eeb6e11c81a33c</id>
<content type='text'>
The EEPROM is compressed on AR9003, upon decompression
the wrong upper limit was being used for the block which
prevented the 5 GHz CTL indexes from being used, which are
stored towards the end of the EEPROM block. This fix allows
the actual intended regulatory limits to be used on AR9003
hardware.

Cc: stable@kernel.org [2.6.36+]
Signed-off-by: Luis R. Rodriguez &lt;lrodriguez@atheros.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The EEPROM is compressed on AR9003, upon decompression
the wrong upper limit was being used for the block which
prevented the 5 GHz CTL indexes from being used, which are
stored towards the end of the EEPROM block. This fix allows
the actual intended regulatory limits to be used on AR9003
hardware.

Cc: stable@kernel.org [2.6.36+]
Signed-off-by: Luis R. Rodriguez &lt;lrodriguez@atheros.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath5k: check return value of ieee80211_get_tx_rate</title>
<updated>2010-08-30T20:01:14+00:00</updated>
<author>
<name>John W. Linville</name>
<email>linville@tuxdriver.com</email>
</author>
<published>2010-08-24T19:27:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=d8e1ba76d619dbc0be8fbeee4e6c683b5c812d3a'/>
<id>d8e1ba76d619dbc0be8fbeee4e6c683b5c812d3a</id>
<content type='text'>
This avoids a NULL pointer dereference as reported here:

	https://bugzilla.redhat.com/show_bug.cgi?id=625889

When the WARN condition is hit in ieee80211_get_tx_rate, it will return
NULL.  So, we need to check the return value and avoid dereferencing it
in that case.

Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Cc: stable@kernel.org
Acked-by: Bob Copeland &lt;me@bobcopeland.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This avoids a NULL pointer dereference as reported here:

	https://bugzilla.redhat.com/show_bug.cgi?id=625889

When the WARN condition is hit in ieee80211_get_tx_rate, it will return
NULL.  So, we need to check the return value and avoid dereferencing it
in that case.

Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Cc: stable@kernel.org
Acked-by: Bob Copeland &lt;me@bobcopeland.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>drivers/net/wireless: Restore upper case words in wiphy_&lt;level&gt; messages</title>
<updated>2010-08-18T20:37:44+00:00</updated>
<author>
<name>Joe Perches</name>
<email>joe@perches.com</email>
</author>
<published>2010-08-12T02:11:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=5db5584441c2dceb75696fb31a44ac7b9b925359'/>
<id>5db5584441c2dceb75696fb31a44ac7b9b925359</id>
<content type='text'>
Commit c96c31e499b70964cfc88744046c998bb710e4b8
"(drivers/net/wireless: Use wiphy_&lt;level&gt;)"
inadvertently changed some upper case words to
lower case.  Restore the original case.

Signed-off-by: Joe Perches &lt;joe@perches.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Commit c96c31e499b70964cfc88744046c998bb710e4b8
"(drivers/net/wireless: Use wiphy_&lt;level&gt;)"
inadvertently changed some upper case words to
lower case.  Restore the original case.

Signed-off-by: Joe Perches &lt;joe@perches.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath5k: disable ASPM L0s for all cards</title>
<updated>2010-08-13T17:46:20+00:00</updated>
<author>
<name>Maxim Levitsky</name>
<email>maximlevitsky@gmail.com</email>
</author>
<published>2010-08-13T15:27:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=6ccf15a1a76d2ff915cdef6ae4d12d0170087118'/>
<id>6ccf15a1a76d2ff915cdef6ae4d12d0170087118</id>
<content type='text'>
Atheros PCIe wireless cards handled by ath5k do require L0s disabled.
For distributions shipping with CONFIG_PCIEASPM (this will be enabled
by default in the future in 2.6.36) this will also mean both L1 and L0s
will be disabled when a pre 1.1 PCIe device is detected. We do know L1
works correctly even for all ath5k pre 1.1 PCIe devices though but cannot
currently undue the effect of a blacklist, for details you can read
pcie_aspm_sanity_check() and see how it adjusts the device link
capability.

It may be possible in the future to implement some PCI API to allow
drivers to override blacklists for pre 1.1 PCIe but for now it is
best to accept that both L0s and L1 will be disabled completely for
distributions shipping with CONFIG_PCIEASPM rather than having this
issue present. Motivation for adding this new API will be to help
with power consumption for some of these devices.

Example of issues you'd see:

  - On the Acer Aspire One (AOA150, Atheros Communications Inc. AR5001
    Wireless Network Adapter [168c:001c] (rev 01)) doesn't work well
    with ASPM enabled, the card will eventually stall on heavy traffic
    with often 'unsupported jumbo' warnings appearing. Disabling
    ASPM L0s in ath5k fixes these problems.

  - On the same card you would see a storm of RXORN interrupts
    even though medium is idle.

Credit for root causing and fixing the bug goes to Jussi Kivilinna.

Cc: David Quan &lt;David.Quan@atheros.com&gt;
Cc: Matthew Garrett &lt;mjg59@srcf.ucam.org&gt;
Cc: Tim Gardner &lt;tim.gardner@canonical.com&gt;
Cc: Jussi Kivilinna &lt;jussi.kivilinna@mbnet.fi&gt;
Cc: stable@kernel.org
Signed-off-by: Luis R. Rodriguez &lt;lrodriguez@atheros.com&gt;
Signed-off-by: Maxim Levitsky &lt;maximlevitsky@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Atheros PCIe wireless cards handled by ath5k do require L0s disabled.
For distributions shipping with CONFIG_PCIEASPM (this will be enabled
by default in the future in 2.6.36) this will also mean both L1 and L0s
will be disabled when a pre 1.1 PCIe device is detected. We do know L1
works correctly even for all ath5k pre 1.1 PCIe devices though but cannot
currently undue the effect of a blacklist, for details you can read
pcie_aspm_sanity_check() and see how it adjusts the device link
capability.

It may be possible in the future to implement some PCI API to allow
drivers to override blacklists for pre 1.1 PCIe but for now it is
best to accept that both L0s and L1 will be disabled completely for
distributions shipping with CONFIG_PCIEASPM rather than having this
issue present. Motivation for adding this new API will be to help
with power consumption for some of these devices.

Example of issues you'd see:

  - On the Acer Aspire One (AOA150, Atheros Communications Inc. AR5001
    Wireless Network Adapter [168c:001c] (rev 01)) doesn't work well
    with ASPM enabled, the card will eventually stall on heavy traffic
    with often 'unsupported jumbo' warnings appearing. Disabling
    ASPM L0s in ath5k fixes these problems.

  - On the same card you would see a storm of RXORN interrupts
    even though medium is idle.

Credit for root causing and fixing the bug goes to Jussi Kivilinna.

Cc: David Quan &lt;David.Quan@atheros.com&gt;
Cc: Matthew Garrett &lt;mjg59@srcf.ucam.org&gt;
Cc: Tim Gardner &lt;tim.gardner@canonical.com&gt;
Cc: Jussi Kivilinna &lt;jussi.kivilinna@mbnet.fi&gt;
Cc: stable@kernel.org
Signed-off-by: Luis R. Rodriguez &lt;lrodriguez@atheros.com&gt;
Signed-off-by: Maxim Levitsky &lt;maximlevitsky@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath9k_htc: load proper firmware for device ID 7015</title>
<updated>2010-08-13T17:46:20+00:00</updated>
<author>
<name>Rajkumar Manoharan</name>
<email>rmanoharan@atheros.com</email>
</author>
<published>2010-08-13T13:06:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=ca6cff1f80f30cc6313a943339361ad6f9e76548'/>
<id>ca6cff1f80f30cc6313a943339361ad6f9e76548</id>
<content type='text'>
This patch handles the firmware loading properly
for device ID 7015.

Signed-off-by: Rajkumar Manoharan &lt;rmanoharan@atheros.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch handles the firmware loading properly
for device ID 7015.

Signed-off-by: Rajkumar Manoharan &lt;rmanoharan@atheros.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath9k_htc: Fix disconnect issue in HT40 mode.</title>
<updated>2010-08-13T17:46:19+00:00</updated>
<author>
<name>Vivek Natarajan</name>
<email>vnatarajan@atheros.com</email>
</author>
<published>2010-08-12T08:53:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=71ba186c123630ddab17667ec9ecf7e2ef211295'/>
<id>71ba186c123630ddab17667ec9ecf7e2ef211295</id>
<content type='text'>
Some APs advertise that they may be HT40 capable in the capabilites
but the current operating channel configuration may be only HT20.
This causes disconnection as ath9k_htc sets WLAN_RC_40_FLAG despite
the AP operating in HT20 mode.
Hence set this flag only if the current channel configuration
is HT40 enabled.

Cc: stable@kernel.org
Signed-off-by: Vivek Natarajan &lt;vnatarajan@atheros.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Some APs advertise that they may be HT40 capable in the capabilites
but the current operating channel configuration may be only HT20.
This causes disconnection as ath9k_htc sets WLAN_RC_40_FLAG despite
the AP operating in HT20 mode.
Hence set this flag only if the current channel configuration
is HT40 enabled.

Cc: stable@kernel.org
Signed-off-by: Vivek Natarajan &lt;vnatarajan@atheros.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath9k_htc: fix panic on packet injection using airbase-ng tool.</title>
<updated>2010-08-11T20:24:43+00:00</updated>
<author>
<name>Rajkumar Manoharan</name>
<email>rmanoharan@atheros.com</email>
</author>
<published>2010-08-11T14:57:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=da93f10684bfba2983a70c10b5d417232b6a5245'/>
<id>da93f10684bfba2983a70c10b5d417232b6a5245</id>
<content type='text'>
This should fix the oops which occurs during the packet injection
on monitor interface.

EIP is at ath9k_htc_tx_start+0x69/0x220 [ath9k_htc]
 [&lt;f84dc8ea&gt;] ? invoke_tx_handlers+0xa5a/0xee0 [mac80211]
 [&lt;f82c84f4&gt;] ? ath9k_htc_tx+0x44/0xe0 [ath9k_htc]
 [&lt;f84db7b8&gt;] ? __ieee80211_tx+0xf8/0x190 [mac80211]
 [&lt;f84dce0d&gt;] ? ieee80211_tx+0x9d/0x1a0 [mac80211]
 [&lt;f84dcfac&gt;] ? ieee80211_xmit+0x9c/0x1c0 [mac80211]
 [&lt;f84dd1b5&gt;] ? ieee80211_monitor_start_xmit+0x85/0xb0 [mac80211]
 [&lt;c04c30cd&gt;] ? dev_hard_start_xmit+0x1ad/0x210
 [&lt;c04b97c2&gt;] ? __alloc_skb+0x52/0x130
 [&lt;c04d7cd5&gt;] ? sch_direct_xmit+0x105/0x170
 [&lt;c04c5e9f&gt;] ? dev_queue_xmit+0x37f/0x4b0
 [&lt;c0567e1e&gt;] ? packet_snd+0x21e/0x250
 [&lt;c05684a2&gt;] ? packet_sendmsg+0x32/0x40
 [&lt;c04b4c63&gt;] ? sock_aio_write+0x113/0x130
 [&lt;c0207934&gt;] ? do_sync_write+0xc4/0x100
 [&lt;c0167740&gt;] ? autoremove_wake_function+0x0/0x50
 [&lt;c02f4414&gt;] ? security_file_permission+0x14/0x20
 [&lt;c0207ad4&gt;] ? rw_verify_area+0x64/0xe0
 [&lt;c01e6458&gt;] ? handle_mm_fault+0x338/0x390
 [&lt;c0207cd5&gt;] ? vfs_write+0x185/0x1a0
 [&lt;c058db20&gt;] ? do_page_fault+0x160/0x3a0
 [&lt;c0208512&gt;] ? sys_write+0x42/0x70
 [&lt;c01033ec&gt;] ? syscall_call+0x7/0xb

Signed-off-by: Rajkumar Manoharan &lt;rmanoharan@atheros.com&gt;
Cc: stable@kernel.org
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This should fix the oops which occurs during the packet injection
on monitor interface.

EIP is at ath9k_htc_tx_start+0x69/0x220 [ath9k_htc]
 [&lt;f84dc8ea&gt;] ? invoke_tx_handlers+0xa5a/0xee0 [mac80211]
 [&lt;f82c84f4&gt;] ? ath9k_htc_tx+0x44/0xe0 [ath9k_htc]
 [&lt;f84db7b8&gt;] ? __ieee80211_tx+0xf8/0x190 [mac80211]
 [&lt;f84dce0d&gt;] ? ieee80211_tx+0x9d/0x1a0 [mac80211]
 [&lt;f84dcfac&gt;] ? ieee80211_xmit+0x9c/0x1c0 [mac80211]
 [&lt;f84dd1b5&gt;] ? ieee80211_monitor_start_xmit+0x85/0xb0 [mac80211]
 [&lt;c04c30cd&gt;] ? dev_hard_start_xmit+0x1ad/0x210
 [&lt;c04b97c2&gt;] ? __alloc_skb+0x52/0x130
 [&lt;c04d7cd5&gt;] ? sch_direct_xmit+0x105/0x170
 [&lt;c04c5e9f&gt;] ? dev_queue_xmit+0x37f/0x4b0
 [&lt;c0567e1e&gt;] ? packet_snd+0x21e/0x250
 [&lt;c05684a2&gt;] ? packet_sendmsg+0x32/0x40
 [&lt;c04b4c63&gt;] ? sock_aio_write+0x113/0x130
 [&lt;c0207934&gt;] ? do_sync_write+0xc4/0x100
 [&lt;c0167740&gt;] ? autoremove_wake_function+0x0/0x50
 [&lt;c02f4414&gt;] ? security_file_permission+0x14/0x20
 [&lt;c0207ad4&gt;] ? rw_verify_area+0x64/0xe0
 [&lt;c01e6458&gt;] ? handle_mm_fault+0x338/0x390
 [&lt;c0207cd5&gt;] ? vfs_write+0x185/0x1a0
 [&lt;c058db20&gt;] ? do_page_fault+0x160/0x3a0
 [&lt;c0208512&gt;] ? sys_write+0x42/0x70
 [&lt;c01033ec&gt;] ? syscall_call+0x7/0xb

Signed-off-by: Rajkumar Manoharan &lt;rmanoharan@atheros.com&gt;
Cc: stable@kernel.org
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath9k: fix erased ieee80211_rx_status.mactime</title>
<updated>2010-08-04T19:28:37+00:00</updated>
<author>
<name>Jan Friedrich</name>
<email>jft@dev2day.de</email>
</author>
<published>2010-08-02T21:55:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=c8f3b7213342d905cbb75d6c8820d9141205f3a0'/>
<id>c8f3b7213342d905cbb75d6c8820d9141205f3a0</id>
<content type='text'>
ath9k_rx_skb_preprocess nulls rxs and the mactime is never set again -
mactime is always 0. This causes problems in IBSS mode.

ieee80211_rx_bss_info uses mactime to decide if an IBSS merge is needed.
Without this patch the merge is triggered by each beacon received.

This can be recognized by the "beacon TSF higher than local TSF - IBSS
merge with BSSID" log message accompanying each beacon.

This problem was not completely fixed in commit
a6d2055b02dde1067075795274672720baadd3ca and is not a stable kernel fix.
It is solely intended for wireless-testing.

Signed-off-by: Jan Friedrich &lt;jft@dev2day.de&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
ath9k_rx_skb_preprocess nulls rxs and the mactime is never set again -
mactime is always 0. This causes problems in IBSS mode.

ieee80211_rx_bss_info uses mactime to decide if an IBSS merge is needed.
Without this patch the merge is triggered by each beacon received.

This can be recognized by the "beacon TSF higher than local TSF - IBSS
merge with BSSID" log message accompanying each beacon.

This problem was not completely fixed in commit
a6d2055b02dde1067075795274672720baadd3ca and is not a stable kernel fix.
It is solely intended for wireless-testing.

Signed-off-by: Jan Friedrich &lt;jft@dev2day.de&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
