<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/net/wireless/ath, branch linux-2.6.37.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.37.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.37.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2011-03-23T19:50:12Z</updated>
<entry>
<title>ath9k: remove support for the FIF_PROMISC_IN_BSS filter flag</title>
<updated>2011-03-23T19:50:12Z</updated>
<author>
<name>Felix Fietkau</name>
</author>
<published>2011-03-09T00:48:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=11503d7c36bb70eff71958ff8946d5b95299f988'/>
<id>urn:sha1:11503d7c36bb70eff71958ff8946d5b95299f988</id>
<content type='text'>
commit 2e286947f1294239527c11f9f466ddce6466455b upstream.

The hardware rx filter flag triggered by FIF_PROMISC_IN_BSS is overly broad
and covers even frames with PHY errors. When this flag is enabled, this message
shows up frequently during scanning or hardware resets:

ath: Could not stop RX, we could be confusing the DMA engine when we start RX up

Since promiscuous mode is usually not particularly useful, yet enabled by
default by bridging (either used normally in 4-addr mode, or with hacks
for various virtualization software), we should sacrifice it for better
reliability during normal operation.

This patch leaves it enabled if there are active monitor mode interfaces, since
it's very useful for debugging.

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 incorrect macversion and macrev checks</title>
<updated>2011-03-23T19:50:11Z</updated>
<author>
<name>Senthil Balasubramanian</name>
</author>
<published>2010-12-22T15:44:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c2ba18104706630ec6e25e0ae7b07e0be048f981'/>
<id>urn:sha1:c2ba18104706630ec6e25e0ae7b07e0be048f981</id>
<content type='text'>
commit ac45c12dfb3f727a5a7a3332ed9c11b4a5ab287e upstream.

There are few places where we are checking for macversion and revsions
before RTC is powered ON. However we are reading the macversion and
revisions only after RTC is powered ON and so both macversion and
revisions are actully zero and this leads to incorrect srev checks

Incorrect srev checks can cause registers to be configured wrongly and can
cause unexpected behavior. Fixing this seems to address the ASPM issue that
we have observed. The laptop becomes very slow and hangs mostly with ASPM L1
enabled without this fix.

fix this by reading the macversion and revisisons even before we start
using them. There is no reason why should we delay reading this info
until RTC is powered on as this is just a register information.

Signed-off-by: Senthil Balasubramanian &lt;senthilkumar@atheros.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: read and backup AR_WA register value even before chip reset on.</title>
<updated>2011-03-23T19:50:10Z</updated>
<author>
<name>Senthil Balasubramanian</name>
</author>
<published>2010-12-22T13:47:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=39780ab15d48a88ca4652d3630808150e4ca2e5f'/>
<id>urn:sha1:39780ab15d48a88ca4652d3630808150e4ca2e5f</id>
<content type='text'>
commit 0a8d7cb0c8182df7a28ad719780071178c386f0f upstream.

We need to read and backup AR_WA register value permanently and reading
this after the chip is awakened results in this register being zeroed out.

This seems to fix the ASPM with L1 enabled issue that we have observed.
The laptop becomes very slow and hangs mostly with ASPM L1 enabled without
this fix.

Signed-off-by: Senthil Balasubramanian &lt;senthilkumar@atheros.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 ath9k prevents CPU to enter C3 states</title>
<updated>2011-03-14T21:17:33Z</updated>
<author>
<name>Mohammed Shafi Shajakhan</name>
</author>
<published>2011-03-04T22:00:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4ae96ec5efcee1c3a5d6665e714d2e7add9533ea'/>
<id>urn:sha1:4ae96ec5efcee1c3a5d6665e714d2e7add9533ea</id>
<content type='text'>
This is a backport of upstream commit 0f5cd45960173ba5b36727decbb4a241cbd35ef9.

The DMA latency issue is observed only in Intel pinetrail platforms
but in the driver we had a default PM-QOS value of 55. This caused
unnecessary power consumption and battery drain in other platforms.

Remove the pm-qos thing in the driver code and address the throughput
issue in Intel pinetrail platfroms in user space using any one of
the scripts in below links:

http://www.kernel.org/pub/linux/kernel/people/mcgrof/scripts/cpudmalatency.c
http://johannes.sipsolutions.net/files/netlatency.c.txt

More details can be found in the following bugzilla link:

https://bugzilla.kernel.org/show_bug.cgi?id=27532

Signed-off-by: Thomas Bächler &lt;thomas@archlinux.org&gt;
Acked-by: Mohammed Shafi Shajakhan &lt;mshajakhan@atheros.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>carl9170: add Airlive X.USB a/b/g/n USBID</title>
<updated>2011-03-07T23:05:25Z</updated>
<author>
<name>Jan Puk</name>
</author>
<published>2011-02-22T13:49:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5d70c044346d70fb9c4980da7c5c581260f41305'/>
<id>urn:sha1:5d70c044346d70fb9c4980da7c5c581260f41305</id>
<content type='text'>
commit c86664e5a285af1afa06416e450e7c4af04daa7c upstream.

"AirLive X.USB now works perfectly under a Linux
environment!"

Signed-off-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@suse.de&gt;

</content>
</entry>
<entry>
<title>ath9k_htc: Fix an endian issue</title>
<updated>2011-03-07T23:05:24Z</updated>
<author>
<name>Sujith Manoharan</name>
</author>
<published>2011-02-27T03:53:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=523e19477be751191853ae6f7bbf32654f7ee9d9'/>
<id>urn:sha1:523e19477be751191853ae6f7bbf32654f7ee9d9</id>
<content type='text'>
commit 2c27392dc4d4f5ee8a3967a520b8f6cac0418031 upstream.

The stream length/tag fields have to be in little endian
format. Fixing this makes the driver work on big-endian
platforms.

Tested-by: raghunathan.kailasanathan@wipro.com
Signed-off-by: Sujith Manoharan &lt;Sujith.Manoharan@atheros.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>carl9170: fix typo in PS code</title>
<updated>2011-02-17T23:14:31Z</updated>
<author>
<name>Christian Lamparter</name>
</author>
<published>2011-02-03T21:22:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=653779ea4311a543968c3f042139c2cac3903310'/>
<id>urn:sha1:653779ea4311a543968c3f042139c2cac3903310</id>
<content type='text'>
commit 5820de5303f73d48dcc3a053c875d1f0da7eef67 upstream.

This patch fixes a off-by-one bug which bugged
the driver's PS-POLL capability.

Signed-off-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@suse.de&gt;

</content>
</entry>
<entry>
<title>ath: Missed to clear key4 of micentry</title>
<updated>2011-02-17T23:13:56Z</updated>
<author>
<name>Rajkumar Manoharan</name>
</author>
<published>2010-12-08T14:31:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bcd4fd6f957ec3cccdfa99e9aecc712fe4a35225'/>
<id>urn:sha1:bcd4fd6f957ec3cccdfa99e9aecc712fe4a35225</id>
<content type='text'>
commit 998d516d9546eba04dd99ae49a78acb0cf770478 upstream.

key4 of micentry is used, if ATH_CRYPT_CAP_MIC_COMBINED is set.
But is not cleared on key cache reset.

Signed-off-by: Rajkumar Manoharan &lt;rmanoharan@atheros.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 system hang when resuming from S3/S4</title>
<updated>2011-02-17T23:13:56Z</updated>
<author>
<name>Rajkumar Manoharan</name>
</author>
<published>2011-01-27T13:09:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bb0a047d608342d23717beb7a5005ef34119592c'/>
<id>urn:sha1:bb0a047d608342d23717beb7a5005ef34119592c</id>
<content type='text'>
commit 5b64aa72ead6f8be488d2be7af579f0d69fb7a6e upstream.

The bit 6 &amp; 7 of AR_WA (0x4004) should be enabled only
for the chips that are supporting L0s functionality
while resuming back from S3/S4.

Enabling these bits for AR9280 is causing system hang
within a few S3/S4-resume cycles.

Cc: Jack Lee &lt;jlee@atheros.com&gt;
Signed-off-by: Rajkumar Manoharan &lt;rmanoharan@atheros.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: disabled PAPRD for AR9003</title>
<updated>2011-02-17T23:13:56Z</updated>
<author>
<name>Luis R. Rodriguez</name>
</author>
<published>2011-01-21T01:47:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=753f1e0a1b142d08f2d9212843c275fbc62ffa51'/>
<id>urn:sha1:753f1e0a1b142d08f2d9212843c275fbc62ffa51</id>
<content type='text'>
commit 6f4810101a629b31b5427872a09ea092cfc5c4bd upstream.

AR9003's PAPRD was enabled prematurely, and is causing some
large discrepancies on throughput and network connectivity.
For example downlink (RX) throughput against an AR9280 AP
can vary widlely from 43-73 Mbit/s while disabling this
gets AR9382 (2x2) up to around 93 Mbit/s in a 2.4 GHz HT20 setup.

Cc: Paul Shaw &lt;paul.shaw@atheros.com&gt;
Signed-off-by: Luis R. Rodriguez &lt;lrodriguez@atheros.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>
