<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/drivers/net/wireless/rt2x00/rt2800lib.c, branch linux-4.1.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.1.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.1.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2015-01-08T14:27:52Z</updated>
<entry>
<title>cfg80211: remove "channel" from survey names</title>
<updated>2015-01-08T14:27:52Z</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2014-11-14T15:35:34Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=4ed20bebf51578229a1986efcf46344075ec8447'/>
<id>urn:sha1:4ed20bebf51578229a1986efcf46344075ec8447</id>
<content type='text'>
All of the survey data is (currently) per channel anyway,
so having the word "channel" in the name does nothing. In
the next patch I'll introduce global data to the survey,
where the word "channel" is actually confusing.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>rt2800: calculate tx power temperature compensation on selected chips</title>
<updated>2014-12-01T20:57:20Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2014-11-25T14:17:29Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=87dd2d76a94b310c173943a7de9a8b6598af0c78'/>
<id>urn:sha1:87dd2d76a94b310c173943a7de9a8b6598af0c78</id>
<content type='text'>
Currently implemented temperature compensation is only valid on some of
supported chips. Other chips do not need temperature compensation or
need different way to do this (not yet implemented in the rt2800
driver). Trying to do run rt2800_get_gain_calibration_delta() when this
is not appropriate on particular chip gives bogus result of TX power
and can make connection unstable.

This is follow up to commit 8c8d2017ba25c510ddf093419048460db1109bc4
"rt2800: fix RT5390 &amp; RT3290 TX power settings regression". On that
commit we avoid setting BBP_R1 register, but the real problem is wrong
temperature compensation calculation.

Reported-and-tested-by: Ronald Wahl &lt;ronald.wahl@raritan.com&gt;
Debugged-by: Ronald Wahl &lt;ronald.wahl@raritan.com&gt;
Cc: Mike Romberg &lt;mike-romberg@comcast.net&gt;
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>rt2x00: support Ralink 5362.</title>
<updated>2014-08-28T18:49:39Z</updated>
<author>
<name>Canek Peláez Valdés</name>
<email>canek@ciencias.unam.mx</email>
</author>
<published>2014-08-25T00:06:11Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=ac0372abf8524a7572a9cdaac6495eb2eba20457'/>
<id>urn:sha1:ac0372abf8524a7572a9cdaac6495eb2eba20457</id>
<content type='text'>
Signed-off-by: Canek Peláez Valdés &lt;canek@ciencias.unam.mx&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>rt2x00: do not initialize BCN_OFFSET registers</title>
<updated>2014-06-19T19:49:15Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2014-06-05T11:52:27Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=19dcb76842d6d51690188c49c5c3142077f8ec5a'/>
<id>urn:sha1:19dcb76842d6d51690188c49c5c3142077f8ec5a</id>
<content type='text'>
We setup BCN_OFFSET{0,1} registers dynamically, don't have to
initialize them.

Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>rt2x00: change default MAC_BSSID_DW1_BSS_BCN_NUM</title>
<updated>2014-06-19T19:49:15Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2014-06-05T11:52:25Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=88ff2f45f23eb0f0e262251b34edb4582ce8e188'/>
<id>urn:sha1:88ff2f45f23eb0f0e262251b34edb4582ce8e188</id>
<content type='text'>
We setup MAC_BSSID_DW1_BSS_BCN_NUM dynamically when numbers of active
beacons increase. Change default to 0 to tell hardware that we want to
send only one beacon as default.

Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>rt2x00: change beaconing setup on RT2800</title>
<updated>2014-06-19T19:49:15Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2014-06-05T11:52:24Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=ba08910e04e09088cac42ab6d5ceedd1239a3208'/>
<id>urn:sha1:ba08910e04e09088cac42ab6d5ceedd1239a3208</id>
<content type='text'>
As reported by Matthias, on 5572 chip, even if we clear up TXWI
of corresponding beacon, hardware still try to send it or do other
action that increase power consumption peak up to 1A.

To avoid the issue, setup beaconing dynamically by configuring offsets
of currently active beacons and MAC_BSSID_DW1_BSS_BCN_NUM variable,
which limit number of beacons that hardware will try to send.

Reported-by: Matthias Fend &lt;Matthias.Fend@wolfvision.net&gt;
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Acked-by: Helmut Schaa &lt;helmut.schaa@googlemail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>rt2x00: restore original beaconing state</title>
<updated>2014-04-22T19:06:31Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2014-04-17T09:08:48Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=bc0df75aea666d855c4111003dbbb197460b6642'/>
<id>urn:sha1:bc0df75aea666d855c4111003dbbb197460b6642</id>
<content type='text'>
After changing local per interface beacon setting restore original
global beaconing state.

Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>Revert "rt2x00: rt2800lib: Update BBP register initialization for RT53xx"</title>
<updated>2014-03-13T18:57:27Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2014-03-12T14:14:04Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=584221918925f0d3bbc8ff6de9cfdb703c06a29c'/>
<id>urn:sha1:584221918925f0d3bbc8ff6de9cfdb703c06a29c</id>
<content type='text'>
This reverts commit eac40d9631a7db43570df859fa8a9922e9623607. It cause
random connection drops on RT5390 PCI adapters.

On Mediatek there is different driver version available for RT53xx chip
based on bus type (2.5.0.3 for PCI and 2.6.1.3 for USB). Hence possibly
we should set registers differently based on bus type. But is also
possible that new driver (i.e. 2.6.1.3) was not verified on RT53xx USB.

Until we figure out how to initialize registers properly for RT53xx just
revert commit eac40d9631a7db43570df859fa8a9922e9623607 since it cause
regression.

Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>rt2800: disable PS by default on USB</title>
<updated>2014-02-04T20:30:06Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2014-01-29T16:42:37Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=58e33a219298c5ba0f88ce9a7d0f448eb3ae884a'/>
<id>urn:sha1:58e33a219298c5ba0f88ce9a7d0f448eb3ae884a</id>
<content type='text'>
We have disabled it currently on other buses. PS can cause some issues,
not necessarily with our driver but on AP, that are not easy to debug.
Since behaviour differs on rt2800usb and rt2800pci, user usually blame
for malfunction rt2800usb driver, whereas issue is on AP side.

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;
</content>
</entry>
<entry>
<title>rt2x00: Fix FSF address in file headers</title>
<updated>2013-12-11T15:56:19Z</updated>
<author>
<name>Jeff Kirsher</name>
<email>jeffrey.t.kirsher@intel.com</email>
</author>
<published>2013-12-06T11:32:11Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=a05b8c580c83a7bd4fce81f8d6af044e97e4a7a4'/>
<id>urn:sha1:a05b8c580c83a7bd4fce81f8d6af044e97e4a7a4</id>
<content type='text'>
Several files refer to an old address for the Free Software Foundation
in the file header comment.  Resolve by replacing the address with
the URL &lt;http://www.gnu.org/licenses/&gt; so that we do not have to keep
updating the header comments anytime the address changes.

CC: linux-wireless@vger.kernel.org
CC: Ivo van Doorn &lt;IvDoorn@gmail.com&gt;
CC: Gertjan van Wingerde &lt;gwingerde@gmail.com&gt;
CC: Helmut Schaa &lt;helmut.schaa@googlemail.com&gt;
Signed-off-by: Jeff Kirsher &lt;jeffrey.t.kirsher@intel.com&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>
