<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/net/wireless/rt2x00/rt2800lib.c, branch linux-3.9.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.9.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.9.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2013-07-03T17:55:22Z</updated>
<entry>
<title>rt2800: fix RT5390 &amp; RT3290 TX power settings regression</title>
<updated>2013-07-03T17:55:22Z</updated>
<author>
<name>Stanislaw Gruszka</name>
</author>
<published>2013-06-11T16:48:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a31da56adfdbc020f1edbc308be17599a465ee6d'/>
<id>urn:sha1:a31da56adfdbc020f1edbc308be17599a465ee6d</id>
<content type='text'>
commit 8c8d2017ba25c510ddf093419048460db1109bc4 upstream.

My change:

commit cee2c7315f60beeff6137ee59e99acc77d636eeb
Author: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Date:   Fri Oct 5 13:44:09 2012 +0200

    rt2800: use BBP_R1 for setting tx power

unfortunately does not work well with RT5390 and RT3290 chips as they
require different temperature compensation TX power settings (TSSI
tuning). Since that commit make wireless connection very unstable on
those chips, restore previous behavior to fix regression. Once we
implement proper TSSI tuning on 5390/3290 we can restore back setting
TX power by BBP_R1 register for those chips.

Reported-and-tested-by: Mike Romberg &lt;mike-romberg@comcast.net&gt;
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Acked-by: Gertjan van Wingerde &lt;gwingerde@gmail.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>rt2x00: Fix transmit power troubles on some Ralink RT30xx cards</title>
<updated>2013-05-08T03:33:08Z</updated>
<author>
<name>Alex A. Mihaylov</name>
</author>
<published>2013-04-15T03:29:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4a277ad651b9ea753feda441aa010aedbf10268d'/>
<id>urn:sha1:4a277ad651b9ea753feda441aa010aedbf10268d</id>
<content type='text'>
commit 7e9dafd873034dd64ababcb858be424c4780ae13 upstream.

Some cards on Ralink RT30xx chipset not have correctly TX_MIXER_GAIN
value in them EEPROM/EFUSE. In this case, we must use default value,
but always used EEPROM/EFUSE value. As result we have tranmitt power
range from -10dBm to +6dBm instead 0dBm to +16dBm.

Correctly value in EEPROM/EFUSE is one or more for RT3070 and two or
more for other RT30xx chips.

Tested on Canyon CNP-WF518N1 usb Wi-Fi dongle and Jorjin WN8020 usb
embedded Wi-Fi module.

Signed-off-by: Alex A. Mihaylov &lt;minimumlaw@rambler.ru&gt;
Acked-by: Gertjan van Wingerde &lt;gwingerde@gmail.com&gt;
Acked-by: Stanislaw Gruszka &lt;sgruszka@redhat.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>rt2x00: remove NOTICE</title>
<updated>2013-01-30T20:06:43Z</updated>
<author>
<name>Stanislaw Gruszka</name>
</author>
<published>2013-01-26T17:13:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=92941382e8b80c55a4ad06b88a3bf95110969693'/>
<id>urn:sha1:92941382e8b80c55a4ad06b88a3bf95110969693</id>
<content type='text'>
We use this macro only on 3 places - remove it and replace by other
appropriate macros for printing messages.

Signed-off-by: Stanislaw Gruszka &lt;stf_xl@wp.pl&gt;
Acked-by: Ivo van Doorn &lt;IvDoorn@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>rt2x00: Improve TX status handling for BlockAckReq frames</title>
<updated>2013-01-22T21:01:29Z</updated>
<author>
<name>Helmut Schaa</name>
</author>
<published>2013-01-17T16:34:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=84e9e8ebd369679a958200a8baca96aafb2393bb'/>
<id>urn:sha1:84e9e8ebd369679a958200a8baca96aafb2393bb</id>
<content type='text'>
Since rt2800 hardware isn't capable of reporting the TX status of
BlockAckReq frames implement the TX status handling of BARs in
rt2x00lib. We keep track of all BARs that are send out and try to
match incoming BAs to the appropriate BARs. This allows us to report a
more or less accurate TX status for BAR frames which in turn improves
BA session stability.

This is loosley based on Christian Lamparter's patch for carl9170
"carl9170: fix HT peer BA session corruption".

We have to walk the list of pending BARs for every rx'red BA even
though most BAs don't belong to any of these BARs as they are just
acknowledging an AMPDU. To keep that overhead low use RCU which allows
us to walk the list of pending BARs without the need to acquire a lock.
This however requires us to _copy_ relevant information from the BAR
(RA, TA, control field, start sequence number) into our BAR list entry.

Signed-off-by: Helmut Schaa &lt;helmut.schaa@googlemail.com&gt;
Tested-by: Andreas Hartmann &lt;andihartmann@01019freenet.de&gt;
Acked-by: Gertjan van Wingerde &lt;gwingerde@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>rt2x00: rt2800: convert read_eeprom functions to return an int value</title>
<updated>2013-01-07T20:16:54Z</updated>
<author>
<name>Gabor Juhos</name>
</author>
<published>2012-12-29T13:51:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a02308e931ad0bba19803779bec491c4b2d67b47'/>
<id>urn:sha1:a02308e931ad0bba19803779bec491c4b2d67b47</id>
<content type='text'>
Both the rtt2x00usb_eeprom_read and the ioremap
functions are allowed to fail, however their
return values are not checked in the read_eeprom
functions in the rt2800{pci,usb} drivers.

The patch adds the missing checks, and converts
all read_eeprom functions to return an int value,
so the error values can be propagated up to the
'rt2800_validate_eeprom' function.

Signed-off-by: Gabor Juhos &lt;juhosg@openwrt.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>rt2800: refactor RFCSR initialization</title>
<updated>2013-01-07T20:16:50Z</updated>
<author>
<name>Stanislaw Gruszka</name>
</author>
<published>2012-12-12T05:30:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d5374ef13ebda6ec93f0b4af6b30682ea4b14782'/>
<id>urn:sha1:d5374ef13ebda6ec93f0b4af6b30682ea4b14782</id>
<content type='text'>
rt2800_init_rfcsr() is too big, split RF initialization into per chip
functions. Code will change, but we should setup the same values onto
RF registers and in the same order as before.

Signed-off-by: Stanislaw Gruszka &lt;stf_xl@wp.pl&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>mac80211: split TX aggregation stop action</title>
<updated>2013-01-03T12:01:42Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2012-07-18T11:51:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=18b559d5db47c86b10c14590aa2d26c0243c39e4'/>
<id>urn:sha1:18b559d5db47c86b10c14590aa2d26c0243c39e4</id>
<content type='text'>
When TX aggregation is stopped, there are a few
different cases:
 - connection with the peer was dropped
 - session stop was requested locally
 - session stop was requested by the peer
 - connection was dropped while a session is stopping

The behaviour in these cases should be different, if
the connection is dropped then the driver should drop
all frames, otherwise the frames may continue to be
transmitted, aggregated in the case of a locally
requested session stop or unaggregated in the case of
the peer requesting session stop.

Split these different cases so that the driver can
act accordingly; however, treat local and remote stop
the same way and ask the driver to not send frames as
aggregated packets any more.

In the case of connection drop, the stop callback the
driver is otherwise supposed to call is no longer
required.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'for-john' of git://git.sipsolutions.net/mac80211-next</title>
<updated>2012-12-11T21:04:03Z</updated>
<author>
<name>John W. Linville</name>
</author>
<published>2012-12-11T21:04:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c66cfd5325bb215a251f4685fac8718b1da33197'/>
<id>urn:sha1:c66cfd5325bb215a251f4685fac8718b1da33197</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Revert: "rt2x00: Don't let mac80211 send a BAR when an AMPDU subframe fails"</title>
<updated>2012-12-05T08:57:19Z</updated>
<author>
<name>Stanislaw Gruszka</name>
</author>
<published>2012-12-03T11:59:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ab9d6e4ffe192427ce9e93d4f927b0faaa8a941e'/>
<id>urn:sha1:ab9d6e4ffe192427ce9e93d4f927b0faaa8a941e</id>
<content type='text'>
This revert:

commit be03d4a45c09ee5100d3aaaedd087f19bc20d01f
Author: Andreas Hartmann &lt;andihartmann@01019freenet.de&gt;
Date:   Tue Apr 17 00:25:28 2012 +0200

    rt2x00: Don't let mac80211 send a BAR when an AMPDU subframe fails

To fix problem workaround by above commit use
IEEE80211_HW_TEARDOWN_AGGR_ON_BAR_FAIL flag (see change log for
"mac80211: introduce IEEE80211_HW_TEARDOWN_AGGR_ON_BAR_FAIL" patch).

Resolve: https://bugzilla.kernel.org/show_bug.cgi?id=42828
Bisected-by: Francisco Pina Martins &lt;f.pinamartins@gmail.com&gt;
Cc: stable@vger.kernel.org
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>rt2x00: rt2800lib: introduce RFCSR3_VCOCAL_EN</title>
<updated>2012-12-03T18:52:01Z</updated>
<author>
<name>Gabor Juhos</name>
</author>
<published>2012-12-02T17:34:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d6d82020d07711f0095f2925bc1b9a28f94bb9b5'/>
<id>urn:sha1:d6d82020d07711f0095f2925bc1b9a28f94bb9b5</id>
<content type='text'>
On the RF3290,RF5360,RF5370,RF5372,RF5390,RF5392
radio frontends, the VCO calibration can be
controlled via the RFCSR3 register. The current
code uses the RFCSR30_RF_CALIBRATION constant to
enable the calibration, however that belongs to
the RFCSR30 register. Although the values of the
constant is correct, but using that for another
register is confusing.

Add a new definition for the VCO calibration enable
bit of the RFCSR3 register and use that in the
relevant places in order to avoid confusions.

The patch contains no functional changes.

Signed-off-by: Gabor Juhos &lt;juhosg@openwrt.org&gt;
Acked-by: Gertjan van Wingerde &lt;gwingerde@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
</feed>
