<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/net/wireless/ath, branch linux-2.6.31.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.31.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.31.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2010-04-01T22:55:29Z</updated>
<entry>
<title>ath5k: Fix eeprom checksum check for custom sized eeproms</title>
<updated>2010-04-01T22:55:29Z</updated>
<author>
<name>Luis R. Rodriguez</name>
</author>
<published>2010-01-04T15:40:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=98e4c05d2401863414cb5183e4d844ad061598ef'/>
<id>urn:sha1:98e4c05d2401863414cb5183e4d844ad061598ef</id>
<content type='text'>
commit 359207c687cc8f4f9845c8dadd0d6dabad44e584 upstream.

Commit 8bf3d79bc401ca417ccf9fc076d3295d1a71dbf5 enabled EEPROM
checksum checks to avoid bogus bug reports but failed to address
updating the code to consider devices with custom EEPROM sizes.
Devices with custom sized EEPROMs have the upper limit size stuffed
in the EEPROM. Use this as the upper limit instead of the static
default size. In case of a checksum error also provide back the
max size and whether or not this was the default size or a custom
one. If the EEPROM is busted we add a failsafe check to ensure
we don't loop forever or try to read bogus areas of hardware.

This closes bug 14874

http://bugzilla.kernel.org/show_bug.cgi?id=14874

Cc: stable@kernel.org
Cc: David Quan &lt;david.quan@atheros.com&gt;
Cc: Stephen Beahm &lt;stephenbeahm@comcast.net&gt;
Reported-by: Joshua Covington &lt;joshuacov@googlemail.com&gt;
Signed-off-by: Luis R. Rodriguez &lt;lrodriguez@atheros.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;

</content>
</entry>
<entry>
<title>ath5k: enable EEPROM checksum check</title>
<updated>2009-12-18T21:43:18Z</updated>
<author>
<name>Luis R. Rodriguez</name>
</author>
<published>2009-11-25T22:23:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0027ce4116e62c943f61f8db8cd92e0d538257a4'/>
<id>urn:sha1:0027ce4116e62c943f61f8db8cd92e0d538257a4</id>
<content type='text'>
commit 512414b0bed0d376ac4d5ec1dd6f0b1a3551febc upstream.

Without this we have no gaurantee of the integrity of the
EEPROM and are likely to encounter a lot of bogus bug reports
due to actual issues on the EEPROM. With the EEPROM checksum
check in place we can easily rule those issues out.

If you run patch during a revert *you* have a card with a busted
EEPROM and only older kernel will support that concoction. This
patch is a trade off between not accepitng bogus EEPROMs and
avoiding bogus bug reports allowing developers to focus instead
on real concrete issues.

If stable keeps bogus bug reports because of a possibly busted EEPROM
feel free to apply this there too.

Tested on an AR5414

Cc: jirislaby@gmail.com
Cc: akpm@linux-foundation.org
Cc: rjw@sisk.pl
Cc: me@bobcopeland.com
Cc: david.quan@atheros.com
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>
<entry>
<title>ath5k: allow setting txpower to 0</title>
<updated>2009-12-18T21:43:18Z</updated>
<author>
<name>Bob Copeland</name>
</author>
<published>2009-11-16T13:30:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=264eaee38a94afb926d57e5c6df52013092d27bf'/>
<id>urn:sha1:264eaee38a94afb926d57e5c6df52013092d27bf</id>
<content type='text'>
commit 2eb2fa67e5462a36e98172fb92c78bc405b3035f upstream.

As a holdover from earlier code when we used to set
the power limit to '0' after a reset to configure the
default transmit power, ath5k interprets txpower=0 as
12.5 dBm.  Fix that by just passing 0 through.

This fixes http://bugzilla.kernel.org/show_bug.cgi?id=14567

Reported-by: Daniel Folkers &lt;daniel.folkers@task24.nl&gt;
Tested-by: Daniel Folkers &lt;daniel.folkers@task24.nl&gt;
Signed-off-by: Bob Copeland &lt;me@bobcopeland.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>ath5k: Linear PCDAC code fixes</title>
<updated>2009-12-08T18:22:37Z</updated>
<author>
<name>Nick Kossifidis</name>
</author>
<published>2009-08-10T00:27:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d02b2ced79e2a22b38d6a4fdc758d070ff807d2b'/>
<id>urn:sha1:d02b2ced79e2a22b38d6a4fdc758d070ff807d2b</id>
<content type='text'>
commit d1cb0bdac180a4afdd3c001acb2618d2a62d9abe upstream.

* Set correct xpd curve indices for high/low gain curves during
   rfbuffer setup on RF5112B with both calibration curves available.

 * Don't return zero min power when we have the same pcdac value
   twice because it breaks interpolation. Instead return the right
   x barrier as we do when we have equal power levels for 2 different
   pcdac values.

Signed-off-by: Nick Kossifidis &lt;mickflemm@gmail.com&gt;
Acked-by: Bob Copeland &lt;me@bobcopeland.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Cc: Dan Williams &lt;dcbw@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ath5k: do not release irq across suspend/resume</title>
<updated>2009-10-05T16:32:32Z</updated>
<author>
<name>Bob Copeland</name>
</author>
<published>2009-07-04T16:59:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=956dc371fe5411ed8a22f1857df3c97f61e9c0c9'/>
<id>urn:sha1:956dc371fe5411ed8a22f1857df3c97f61e9c0c9</id>
<content type='text'>
commit 0d0cd72fa1e6bfd419c99478ec70b4877ed0ef86 upstream.

Paraphrasing Rafael J. Wysocki: "drivers should not release PCI IRQs
in suspend."  Doing so causes a warning during suspend/resume on some
platforms.

Cc: Rafael J. Wysocki &lt;rjw@sisk.pl&gt;
Reported-by: Alan Jenkins &lt;alan-jenkins@tuffmail.co.uk&gt;
Signed-off-by: Bob Copeland &lt;me@bobcopeland.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>ath5k: Wakeup fixes</title>
<updated>2009-10-05T16:32:32Z</updated>
<author>
<name>Nick Kossifidis</name>
</author>
<published>2009-08-10T00:29:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a5901d2b8dc71e82e3ba2af5f54f4fdee5bf8f04'/>
<id>urn:sha1:a5901d2b8dc71e82e3ba2af5f54f4fdee5bf8f04</id>
<content type='text'>
commit edd7fc7003f31da48d06e215a93ea966a22c2a03 upstream.

* Don't put chip to full sleep because there are problems during
   wakeup. Instead hold MAC/Baseband on warm reset state via a new
   function ath5k_hw_on_hold.

 * Minor cleanups

Signed-off-by: Nick Kossifidis &lt;mickflemm@gmail.com&gt;
Tested-by: Ben Greear &lt;greearb@candelatech.com&gt;
Tested-by: Johannes Stezenbach &lt;js@sig21.net&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>ar9170usb: add usbid for TP-Link TL-WN821N v2</title>
<updated>2009-10-05T16:31:50Z</updated>
<author>
<name>Christian Lamparter</name>
</author>
<published>2009-09-17T11:46:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a9e31b939c86bc6cb6989ed542ff5b3c77446e0d'/>
<id>urn:sha1:a9e31b939c86bc6cb6989ed542ff5b3c77446e0d</id>
<content type='text'>
commit fe9f6342c86292aee1941447f22dc5470735e5a1 upstream.

This patch adds the usbid for TP-Link TL-WN821N v2.

Reported-by: Fabian Lenz &lt;lenz_fabian@yahoo.de&gt;
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>ath5k: write PCU registers on initial reset</title>
<updated>2009-09-24T15:43:51Z</updated>
<author>
<name>Bob Copeland</name>
</author>
<published>2009-07-05T01:03:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3cfbbe0e83024a77c9626977f1d59224b9f92860'/>
<id>urn:sha1:3cfbbe0e83024a77c9626977f1d59224b9f92860</id>
<content type='text'>
commit 3355443ad7601991affa5992b0d53870335af765 upstream.

"Ath5k: unify resets"
introduced a regression into 2.6.28 where the PCU registers are never
initialized, due to ath5k_reset() always passing true for change_channel.
We subsequently program a lot of these registers but several may start
in an unknown state.

Reported-by: Forrest Zhang &lt;forrest@hifulltech.com&gt;
Signed-off-by: Bob Copeland &lt;me@bobcopeland.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>ar9170: fix read &amp; write outside array bounds</title>
<updated>2009-08-10T20:41:01Z</updated>
<author>
<name>Dan Carpenter</name>
</author>
<published>2009-08-09T12:24:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e9d126cdfa60b575f1b5b02024c4faee27dccf07'/>
<id>urn:sha1:e9d126cdfa60b575f1b5b02024c4faee27dccf07</id>
<content type='text'>
queue == __AR9170_NUM_TXQ would cause a bug on the next line.

found by Smatch ( http://repo.or.cz/w/smatch.git ).

Cc: stable@kernel.org
Reported-by: Dan Carpenter &lt;error27@gmail.com&gt;
Signed-off-by: Dan Carpenter &lt;error27@gmail.com&gt;
Signed-off-by: Christian Lamparter &lt;chunkeey@web.de&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>ar9170usb: fix spurious firmware related message</title>
<updated>2009-08-10T20:41:01Z</updated>
<author>
<name>Christian Lamparter</name>
</author>
<published>2009-08-08T15:09:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=363ec5614f86110c6a6bdd72ac2147ebafd3ff5e'/>
<id>urn:sha1:363ec5614f86110c6a6bdd72ac2147ebafd3ff5e</id>
<content type='text'>
When ar9170-2.fw was missing, the driver erroneously complained
about missing the initialization values file ar9170-1.fw...

Signed-off-by: Christian Lamparter &lt;chunkeey@web.de&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
</feed>
