<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/net/wireless/ath, branch v3.0.26</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/net/wireless/ath?h=v3.0.26</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/net/wireless/ath?h=v3.0.26'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2012-03-12T17:33:01Z</updated>
<entry>
<title>carl9170: Fix memory accounting when sta is in power-save mode.</title>
<updated>2012-03-12T17:33:01Z</updated>
<author>
<name>Nicolas Cavallari</name>
<email>Nicolas.Cavallari@lri.fr</email>
</author>
<published>2012-02-23T15:53:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2070216144d9c8ff4894a443b093277b42342b12'/>
<id>urn:sha1:2070216144d9c8ff4894a443b093277b42342b12</id>
<content type='text'>
commit 992d52529d7840236d3059b51c15d5eb9e81a869 upstream.

On Access Point mode, when transmitting a packet, if the destination
station is in powersave mode, we abort transmitting the packet to the
device queue, but we do not reclaim the allocated memory.  Given enough
packets, we can go in a state where there is no packet on the device
queue, but we think the device has no memory left, so no packet gets
transmitted, connections breaks and the AP stops working.

This undo the allocation done in the TX path when the station is in
power-save mode.

Signed-off-by: Nicolas Cavallari &lt;cavallar@lri.fr&gt;
Acked-by: Christian Lamparter &lt;chunkeey@googlemail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ath9k_hw: prevent writes to const data on AR9160</title>
<updated>2012-03-12T17:32:56Z</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@openwrt.org</email>
</author>
<published>2012-02-15T18:31:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b0f1b35e3cf604dcafdeae9ba3b4a1a86df7d9e8'/>
<id>urn:sha1:b0f1b35e3cf604dcafdeae9ba3b4a1a86df7d9e8</id>
<content type='text'>
commit 9bbb8168ed3d8b946f9c1901a63a675012de88f2 upstream.

Duplicate the data for iniAddac early on, to avoid having to do redundant
memcpy calls later. While we're at it, make AR5416 &lt; v2.2 use the same
codepath. Fixes a reported crash on x86.

Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Reported-by: Magnus Määttä &lt;magnus.maatta@logica.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ath9k: stop on rates with idx -1 in ath9k rate control's .tx_status</title>
<updated>2012-03-01T00:34:28Z</updated>
<author>
<name>Pavel Roskin</name>
<email>proski@gnu.org</email>
</author>
<published>2012-02-11T15:01:53Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6778e220c09cdfb19a326192fd25ee146755b95d'/>
<id>urn:sha1:6778e220c09cdfb19a326192fd25ee146755b95d</id>
<content type='text'>
commit 2504a6423b9ab4c36df78227055995644de19edb upstream.

Rate control algorithms are supposed to stop processing when they
encounter a rate with the index -1.  Checking for rate-&gt;count not being
zero is not enough.

Allowing a rate with negative index leads to memory corruption in
ath_debug_stat_rc().

One consequence of the bug is discussed at
https://bugzilla.redhat.com/show_bug.cgi?id=768639

Signed-off-by: Pavel Roskin &lt;proski@gnu.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ath9k: Fix kernel panic in AR2427 in AP mode</title>
<updated>2012-01-06T22:14:14Z</updated>
<author>
<name>Mohammed Shafi Shajakhan</name>
<email>mohammed@qca.qualcomm.com</email>
</author>
<published>2011-12-26T05:12:15Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=eb1f526d4bfda44e94ccdf34950911eaff74b092'/>
<id>urn:sha1:eb1f526d4bfda44e94ccdf34950911eaff74b092</id>
<content type='text'>
commit b25bfda38236f349cde0d1b28952f4eea2148d3f upstream.

don't do aggregation related stuff for 'AP mode client power save
handling' if aggregation is not enabled in the driver, otherwise it
will lead to panic because those data structures won't be never
intialized in 'ath_tx_node_init' if aggregation is disabled

	EIP is at ath_tx_aggr_wakeup+0x37/0x80 [ath9k]
	EAX: e8c09a20 EBX: f2a304e8 ECX: 00000001 EDX: 00000000
	ESI: e8c085e0 EDI: f2a304ac EBP: f40e1ca4 ESP: f40e1c8c
	DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
	Process swapper/1 (pid: 0, ti=f40e0000 task=f408e860
	task.ti=f40dc000)
	Stack:
	0001e966 e8c09a20 00000000 f2a304ac e8c085e0 f2a304ac
	f40e1cb0 f8186741
	f8186700 f40e1d2c f922988d f2a304ac 00000202 00000001
	c0b4ba43 00000000
	0000000f e8eb75c0 e8c085e0 205b0001 34383220 f2a304ac
	f2a30000 00010020
	Call Trace:
	[&lt;f8186741&gt;] ath9k_sta_notify+0x41/0x50 [ath9k]
	[&lt;f8186700&gt;] ? ath9k_get_survey+0x110/0x110 [ath9k]
	[&lt;f922988d&gt;] ieee80211_sta_ps_deliver_wakeup+0x9d/0x350
	[mac80211]
	[&lt;c018dc75&gt;] ? __module_address+0x95/0xb0
	[&lt;f92465b3&gt;] ap_sta_ps_end+0x63/0xa0 [mac80211]
	[&lt;f9246746&gt;] ieee80211_rx_h_sta_process+0x156/0x2b0
	[mac80211]
	[&lt;f9247d1e&gt;] ieee80211_rx_handlers+0xce/0x510 [mac80211]
	[&lt;c018440b&gt;] ? trace_hardirqs_on+0xb/0x10
	[&lt;c056936e&gt;] ? skb_queue_tail+0x3e/0x50
	[&lt;f9248271&gt;] ieee80211_prepare_and_rx_handle+0x111/0x750
	[mac80211]
	[&lt;f9248bf9&gt;] ieee80211_rx+0x349/0xb20 [mac80211]
	[&lt;f9248949&gt;] ? ieee80211_rx+0x99/0xb20 [mac80211]
	[&lt;f818b0b8&gt;] ath_rx_tasklet+0x818/0x1d00 [ath9k]
	[&lt;f8187a75&gt;] ? ath9k_tasklet+0x35/0x1c0 [ath9k]
	[&lt;f8187a75&gt;] ? ath9k_tasklet+0x35/0x1c0 [ath9k]
	[&lt;f8187b33&gt;] ath9k_tasklet+0xf3/0x1c0 [ath9k]
	[&lt;c0151b7e&gt;] tasklet_action+0xbe/0x180

Cc: Senthil Balasubramanian &lt;senthilb@qca.qualcomm.com&gt;
Cc: Rajkumar Manoharan &lt;rmanohar@qca.qualcomm.com&gt;
Reported-by: Ashwin Mendonca &lt;ashwinloyal@gmail.com&gt;
Tested-by: Ashwin Mendonca &lt;ashwinloyal@gmail.com&gt;
Signed-off-by: Mohammed Shafi Shajakhan &lt;mohammed@qca.qualcomm.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ath9k: fix max phy rate at rate control init</title>
<updated>2012-01-06T22:13:54Z</updated>
<author>
<name>Rajkumar Manoharan</name>
<email>rmanohar@qca.qualcomm.com</email>
</author>
<published>2011-12-10T13:29:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3c00ff7bd542942ff7f3e473d1372b4ae892318f'/>
<id>urn:sha1:3c00ff7bd542942ff7f3e473d1372b4ae892318f</id>
<content type='text'>
commit 10636bc2d60942254bda149827b922c41f4cb4af upstream.

The stations always chooses 1Mbps for all trasmitting frames,
whenever the AP is configured to lock the supported rates.
As the max phy rate is always set with the 4th from highest phy rate,
this assumption might be wrong if we have less than that. Fix that.

Cc: Paul Stewart &lt;pstew@google.com&gt;
Reported-by: Ajay Gummalla &lt;agummalla@google.com&gt;
Signed-off-by: Rajkumar Manoharan &lt;rmanohar@qca.qualcomm.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ath9k_hw: Fix regression of register offset for AR9003 chips</title>
<updated>2011-11-11T17:37:18Z</updated>
<author>
<name>Rajkumar Manoharan</name>
<email>rmanohar@qca.qualcomm.com</email>
</author>
<published>2011-10-20T08:52:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=82eaf854859022f7bf1aa9122ed533516187cbff'/>
<id>urn:sha1:82eaf854859022f7bf1aa9122ed533516187cbff</id>
<content type='text'>
commit 52d6d4ef5e6d1517688e27c11c01ab303ec681dd upstream.

My recent commits (3782c69d, 324c74a) introduced regression
for register offset selection that based on the macversion.
Not using parentheses in proper manner for ternary operator
leads to select wrong offset for the registers.

This issue was observed with AR9462 chip that immediate disconnect
after the association with the following message

ieee80211 phy3: wlan0: Failed to send nullfunc to AP 00:23:69:12:ea:47
after 500ms, disconnecting.

Signed-off-by: Rajkumar Manoharan &lt;rmanohar@qca.qualcomm.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ath9k_hw: Update AR9485 initvals to fix system hang issue</title>
<updated>2011-11-11T17:37:12Z</updated>
<author>
<name>Rajkumar Manoharan</name>
<email>rmanohar@qca.qualcomm.com</email>
</author>
<published>2011-10-24T12:43:40Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1cc8631784f67c62a8309897f7d4cb885a05ed6f'/>
<id>urn:sha1:1cc8631784f67c62a8309897f7d4cb885a05ed6f</id>
<content type='text'>
commit 98fb2cc115b4ef1ea0a2d87a170c183bd395dd6c upstream.

This patch fixes system hang when resuming from S3 state
and lower rate sens failure issue.

Signed-off-by: Rajkumar Manoharan &lt;rmanohar@qca.qualcomm.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ath9k: disable unnecessary PHY error reporting</title>
<updated>2011-11-11T17:35:44Z</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@openwrt.org</email>
</author>
<published>2011-10-08T13:49:57Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=07bb3623343d8060b6f68aa294e3ecb9391a82d4'/>
<id>urn:sha1:07bb3623343d8060b6f68aa294e3ecb9391a82d4</id>
<content type='text'>
commit ac06697c79bad09e44a8b1d52104014016fb90de upstream.

PHY errors relevant for ANI are always tracked by hardware counters, the
bits that allow them to pass through the rx filter are independent of that.
Enabling PHY errors in the rx filter often creates lots of useless DMA traffic
and might be responsible for some of the rx dma stop failure warnings.

Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ath9k_hw: Fix number of GPIO pins for AR9287/9300</title>
<updated>2011-11-11T17:35:44Z</updated>
<author>
<name>Mohammed Shafi Shajakhan</name>
<email>mohammed@qca.qualcomm.com</email>
</author>
<published>2011-09-30T06:01:27Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e4779966c769188b76ee699e0ab476030b2d2e6a'/>
<id>urn:sha1:e4779966c769188b76ee699e0ab476030b2d2e6a</id>
<content type='text'>
commit 6321eb0977b011ac61dfca36e7c69b2c4325b104 upstream.

this patch fixes the assumption of maximum number of GPIO pins present
in AR9287/AR9300. this fix is essential as we might encounter some
functionality issues involved in accessing the status of GPIO pins which
are all incorrectly assumed to be not within the range of max_num_gpio
of AR9300/AR9287 chipsets

Signed-off-by: Mohammed Shafi Shajakhan &lt;mohammed@qca.qualcomm.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ath9k_htc: add AVM FRITZ!WLAN 11N v2 support</title>
<updated>2011-11-11T17:35:44Z</updated>
<author>
<name>Luis R. Rodriguez</name>
<email>mcgrof@qca.qualcomm.com</email>
</author>
<published>2011-09-29T17:42:19Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7ff861f96140c2dc6411deafb281dbfe958324d9'/>
<id>urn:sha1:7ff861f96140c2dc6411deafb281dbfe958324d9</id>
<content type='text'>
commit 8c34559b4a6df32e4af1b073397fa4dc189a5485 upstream.

This was reported and tested by Martin Walter over at AVM GmbH Berlin.
This also applies to 3.0.1 so sendint to stable.

Cc: s.kirste@avm.de
Cc: d.friedel@avm.de
Cc: Martin Walter &lt;m.walter@avm.de&gt;
Cc: Peter Grabienski &lt;pgrabien@qca.qualcomm.com&gt;
Tested-by: Martin Walter &lt;m.walter@avm.de&gt;
Signed-off-by: Luis R. Rodriguez &lt;mcgrof@qca.qualcomm.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
</feed>
