<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux.git/drivers/net/wireless, branch v2.6.39</title>
<subtitle>Linux kernel source tree</subtitle>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/'/>
<entry>
<title>Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6</title>
<updated>2011-05-11T23:13:08+00:00</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2011-05-11T23:13:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=78d41b35a9570b7a9a45686789df5dfaeb2b7f4c'/>
<id>78d41b35a9570b7a9a45686789df5dfaeb2b7f4c</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>libertas: fix cmdpendingq locking</title>
<updated>2011-05-10T19:47:00+00:00</updated>
<author>
<name>Paul Fox</name>
<email>pgf@laptop.org</email>
</author>
<published>2011-05-09T09:40:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=2ae1b8b35faba31a59b153cbad07f9c15de99740'/>
<id>2ae1b8b35faba31a59b153cbad07f9c15de99740</id>
<content type='text'>
We occasionally see list corruption using libertas.

While we haven't been able to diagnose this precisely, we have spotted
a possible cause: cmdpendingq is generally modified with driver_lock
held. However, there are a couple of points where this is not the case.

Fix up those operations to execute under the lock, it seems like
the correct thing to do and will hopefully improve the situation.

Signed-off-by: Paul Fox &lt;pgf@laptop.org&gt;
Signed-off-by: Daniel Drake &lt;dsd@laptop.org&gt;
Acked-by: Dan Williams &lt;dcbw@redhat.com&gt;
Cc: stable@kernel.org
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We occasionally see list corruption using libertas.

While we haven't been able to diagnose this precisely, we have spotted
a possible cause: cmdpendingq is generally modified with driver_lock
held. However, there are a couple of points where this is not the case.

Fix up those operations to execute under the lock, it seems like
the correct thing to do and will hopefully improve the situation.

Signed-off-by: Paul Fox &lt;pgf@laptop.org&gt;
Signed-off-by: Daniel Drake &lt;dsd@laptop.org&gt;
Acked-by: Dan Williams &lt;dcbw@redhat.com&gt;
Cc: stable@kernel.org
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>iwlegacy: fix IBSS mode crashes</title>
<updated>2011-05-10T19:46:59+00:00</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2011-05-07T15:46:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=eb85de3f84868ca85703a23617b4079ce79a801e'/>
<id>eb85de3f84868ca85703a23617b4079ce79a801e</id>
<content type='text'>
We should not switch to non-IBSS channels when working in IBSS mode,
otherwise there are microcode errors, and after some time system
crashes.

This bug is only observable when software scan is used in IBSS mode,
so should be considered as regression after:

commit 0263aa45293838b514b8af674a03faf040991a90
Author: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Date:   Tue Mar 29 11:24:21 2011 +0200

    iwl3945: disable hw scan by default

However IBSS mode check, which this patch add again, was removed by

commit b2f30e8bdd8ef5f3b5a7ef9146509585a15347d3
Author: Johannes Berg &lt;johannes.berg@intel.com&gt;
Date:   Thu Jan 21 07:32:20 2010 -0800

    iwlwifi: remove IBSS channel sanity check

That commit claim that mac80211 will not use non-IBSS channel in IBSS
mode, what definitely is not true. Bug probably should be fixed in
mac80211, but that will require more work, so better to apply that patch
temporally, and provide proper mac80211 fix latter.

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

Reported-and-tested-by: Mikko Rapeli &lt;mikko.rapeli@iki.fi&gt;
Cc: stable@kernel.org # 2.6.38.5+
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We should not switch to non-IBSS channels when working in IBSS mode,
otherwise there are microcode errors, and after some time system
crashes.

This bug is only observable when software scan is used in IBSS mode,
so should be considered as regression after:

commit 0263aa45293838b514b8af674a03faf040991a90
Author: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Date:   Tue Mar 29 11:24:21 2011 +0200

    iwl3945: disable hw scan by default

However IBSS mode check, which this patch add again, was removed by

commit b2f30e8bdd8ef5f3b5a7ef9146509585a15347d3
Author: Johannes Berg &lt;johannes.berg@intel.com&gt;
Date:   Thu Jan 21 07:32:20 2010 -0800

    iwlwifi: remove IBSS channel sanity check

That commit claim that mac80211 will not use non-IBSS channel in IBSS
mode, what definitely is not true. Bug probably should be fixed in
mac80211, but that will require more work, so better to apply that patch
temporally, and provide proper mac80211 fix latter.

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

Reported-and-tested-by: Mikko Rapeli &lt;mikko.rapeli@iki.fi&gt;
Cc: stable@kernel.org # 2.6.38.5+
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath9k: Fix a warning due to a queued work during S3 state</title>
<updated>2011-05-10T19:46:58+00:00</updated>
<author>
<name>Mohammed Shafi Shajakhan</name>
<email>mshajakhan@atheros.com</email>
</author>
<published>2011-05-06T15:13:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=99aa55b66e3553e6f7212ec1104e0fac06cc558e'/>
<id>99aa55b66e3553e6f7212ec1104e0fac06cc558e</id>
<content type='text'>
during suspend/S3 state drv_flush is called from mac80211 irrespective of
interface count. In ath9k we queue a work in ath9k_flush which we expect
to be cancelled in the drv_stop call back. during suspend process mac80211
calls drv_stop only when the interface count(local-&gt;count) is non-zero.
unfortunately when the network manager is enabled, drv_flush is called
while drv_stop is not called as local-&gt;count reaches '0'.
	So fix this by simply checking for the device presence in the
drv_flush call back in the driver before queueing work or anything else.
this patch fixes the following WARNING

	Call Trace:
	[&lt;c014c6e2&gt;] warn_slowpath_common+0x72/0xa0
	[&lt;fc133f99&gt;] ? ieee80211_can_queue_work+0x39/0x50 [mac80211]
	[&lt;fc133f99&gt;] ? ieee80211_can_queue_work+0x39/0x50 [mac80211]
	[&lt;c014c75b&gt;] warn_slowpath_fmt+0x2b/0x30
	[&lt;fc133f99&gt;] ieee80211_can_queue_work+0x39/0x50 [mac80211]
	[&lt;fc134ed1&gt;] ieee80211_queue_delayed_work+0x21/0x50 [mac80211]
	[&lt;fc1e5b22&gt;] ath_tx_complete_poll_work+0xb2/0x100 [ath9k]
	[&lt;c016399e&gt;] run_workqueue+0x8e/0x150
	[&lt;fc1e5a70&gt;] ? ath_tx_complete_poll_work+0x0/0x100 [ath9k]
	[&lt;c0163ae4&gt;] worker_thread+0x84/0xe0
	[&lt;c0167a60&gt;] ? autoremove_wake_function+0x0/0x50
	[&lt;c0163a60&gt;] ? worker_thread+0x0/0xe0
	[&lt;c01677d4&gt;] kthread+0x74/0x80
	[&lt;c0167760&gt;] ? kthread+0x0/0x80
	[&lt;c0104087&gt;] kernel_thread_helper+0x7/0x10
---[ end trace 2aff81010df9215b ]---

Signed-off-by: Rajkumar Manoharan &lt;rmanoharan@atheros.com&gt;
Signed-off-by: Mohammed Shafi Shajakhan &lt;mshajakhan@atheros.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
during suspend/S3 state drv_flush is called from mac80211 irrespective of
interface count. In ath9k we queue a work in ath9k_flush which we expect
to be cancelled in the drv_stop call back. during suspend process mac80211
calls drv_stop only when the interface count(local-&gt;count) is non-zero.
unfortunately when the network manager is enabled, drv_flush is called
while drv_stop is not called as local-&gt;count reaches '0'.
	So fix this by simply checking for the device presence in the
drv_flush call back in the driver before queueing work or anything else.
this patch fixes the following WARNING

	Call Trace:
	[&lt;c014c6e2&gt;] warn_slowpath_common+0x72/0xa0
	[&lt;fc133f99&gt;] ? ieee80211_can_queue_work+0x39/0x50 [mac80211]
	[&lt;fc133f99&gt;] ? ieee80211_can_queue_work+0x39/0x50 [mac80211]
	[&lt;c014c75b&gt;] warn_slowpath_fmt+0x2b/0x30
	[&lt;fc133f99&gt;] ieee80211_can_queue_work+0x39/0x50 [mac80211]
	[&lt;fc134ed1&gt;] ieee80211_queue_delayed_work+0x21/0x50 [mac80211]
	[&lt;fc1e5b22&gt;] ath_tx_complete_poll_work+0xb2/0x100 [ath9k]
	[&lt;c016399e&gt;] run_workqueue+0x8e/0x150
	[&lt;fc1e5a70&gt;] ? ath_tx_complete_poll_work+0x0/0x100 [ath9k]
	[&lt;c0163ae4&gt;] worker_thread+0x84/0xe0
	[&lt;c0167a60&gt;] ? autoremove_wake_function+0x0/0x50
	[&lt;c0163a60&gt;] ? worker_thread+0x0/0xe0
	[&lt;c01677d4&gt;] kthread+0x74/0x80
	[&lt;c0167760&gt;] ? kthread+0x0/0x80
	[&lt;c0104087&gt;] kernel_thread_helper+0x7/0x10
---[ end trace 2aff81010df9215b ]---

Signed-off-by: Rajkumar Manoharan &lt;rmanoharan@atheros.com&gt;
Signed-off-by: Mohammed Shafi Shajakhan &lt;mshajakhan@atheros.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6</title>
<updated>2011-05-02T19:21:47+00:00</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2011-05-02T19:21:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=badb02953aac4af9993163e2a87be60f10700db9'/>
<id>badb02953aac4af9993163e2a87be60f10700db9</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>iwl4965: fix "Received BA when not expected"</title>
<updated>2011-04-29T19:24:15+00:00</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2011-04-29T15:51:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=16b345d89686ca0482a9ca741a1167def1abdd7f'/>
<id>16b345d89686ca0482a9ca741a1167def1abdd7f</id>
<content type='text'>
Need to use broadcast sta_id for management frames, otherwise we broke
BA session in the firmware and get messages like that:

"Received BA when not expected"

or (on older kernels):

"BA scd_flow 0 does not match txq_id 10"

This fix regression introduced in 2.6.35 during station management
code rewrite by:

commit 2a87c26bbe9587baeb9e56d3ce0b4971bd777643
Author: Johannes Berg &lt;johannes.berg@intel.com&gt;
Date:   Fri Apr 30 11:30:45 2010 -0700

    iwlwifi: use iwl_find_station less

Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Need to use broadcast sta_id for management frames, otherwise we broke
BA session in the firmware and get messages like that:

"Received BA when not expected"

or (on older kernels):

"BA scd_flow 0 does not match txq_id 10"

This fix regression introduced in 2.6.35 during station management
code rewrite by:

commit 2a87c26bbe9587baeb9e56d3ce0b4971bd777643
Author: Johannes Berg &lt;johannes.berg@intel.com&gt;
Date:   Fri Apr 30 11:30:45 2010 -0700

    iwlwifi: use iwl_find_station less

Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>iwlagn: fix "Received BA when not expected"</title>
<updated>2011-04-29T19:24:15+00:00</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2011-04-29T15:51:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=bfd36103ec26599557c2bd3225a1f1c9267f8fcb'/>
<id>bfd36103ec26599557c2bd3225a1f1c9267f8fcb</id>
<content type='text'>
Need to use broadcast sta_id for management frames, otherwise we broke
BA session in the firmware and get messages like that:

"Received BA when not expected"

or (on older kernels):

"BA scd_flow 0 does not match txq_id 10"

This fix regression introduced in 2.6.35 during station management
code rewrite by:

commit 2a87c26bbe9587baeb9e56d3ce0b4971bd777643
Author: Johannes Berg &lt;johannes.berg@intel.com&gt;
Date:   Fri Apr 30 11:30:45 2010 -0700

    iwlwifi: use iwl_find_station less

Patch partially resolve:
https://bugzilla.kernel.org/show_bug.cgi?id=16691
However, there are still 11n performance problems on 4965 and 5xxx
devices that need to be investigated.

Cc: stable@kernel.org # 2.6.35+
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Acked-by: Johannes Berg &lt;johannes@sipsolutions.net&gt;
Acked-by: Wey-Yi Guy &lt;wey-yi.w.guy@intel.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Need to use broadcast sta_id for management frames, otherwise we broke
BA session in the firmware and get messages like that:

"Received BA when not expected"

or (on older kernels):

"BA scd_flow 0 does not match txq_id 10"

This fix regression introduced in 2.6.35 during station management
code rewrite by:

commit 2a87c26bbe9587baeb9e56d3ce0b4971bd777643
Author: Johannes Berg &lt;johannes.berg@intel.com&gt;
Date:   Fri Apr 30 11:30:45 2010 -0700

    iwlwifi: use iwl_find_station less

Patch partially resolve:
https://bugzilla.kernel.org/show_bug.cgi?id=16691
However, there are still 11n performance problems on 4965 and 5xxx
devices that need to be investigated.

Cc: stable@kernel.org # 2.6.35+
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Acked-by: Johannes Berg &lt;johannes@sipsolutions.net&gt;
Acked-by: Wey-Yi Guy &lt;wey-yi.w.guy@intel.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>iwl4965: fix "TX Power requested while scanning"</title>
<updated>2011-04-28T18:38:36+00:00</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2011-04-28T09:36:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=f325757ab2812b42da4d690cf8da73c0e678368c'/>
<id>f325757ab2812b42da4d690cf8da73c0e678368c</id>
<content type='text'>
Fix the following:

WARNING: at drivers/net/wireless/iwlegacy/iwl-4965.c:1128 \
iwl4965_send_tx_power+0x61/0x102 [iwl4965]() Hardware name: [...]
TX Power requested while scanning!

Pid: 5723, comm: kworker/u:28 Not tainted 2.6.39-0.rc4.4.fc14.x86_64 #1
Call Trace:
 [&lt;ffffffff8104e27b&gt;] warn_slowpath_common+0x85/0x9d
 [&lt;ffffffffa02782e0&gt;] ? iwl4965_show_temperature+0x49/0x49 [iwl4965]
 [&lt;ffffffff8104e336&gt;] warn_slowpath_fmt+0x46/0x48
 [&lt;ffffffffa027712f&gt;] iwl4965_send_tx_power+0x61/0x102 [iwl4965]
 [&lt;ffffffff81477e05&gt;] ? mutex_lock+0x36/0x50
 [&lt;ffffffffa0278337&gt;] iwl4965_bg_txpower_work+0x57/0x73 [iwl4965]
 [&lt;ffffffff810647f3&gt;] process_one_work+0x18d/0x286
 [&lt;ffffffff81065a5e&gt;] worker_thread+0xfd/0x181
 [&lt;ffffffff81065961&gt;] ? manage_workers.clone.16+0x172/0x172
 [&lt;ffffffff81069036&gt;] kthread+0x82/0x8a
 [&lt;ffffffff81480524&gt;] kernel_thread_helper+0x4/0x10
 [&lt;ffffffff81068fb4&gt;] ? kthread_worker_fn+0x14b/0x14b
 [&lt;ffffffff81480520&gt;] ? gs_change+0x13/0x13

Reported-and-tested-by: Paul Bolle &lt;pebolle@tiscali.nl&gt;
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fix the following:

WARNING: at drivers/net/wireless/iwlegacy/iwl-4965.c:1128 \
iwl4965_send_tx_power+0x61/0x102 [iwl4965]() Hardware name: [...]
TX Power requested while scanning!

Pid: 5723, comm: kworker/u:28 Not tainted 2.6.39-0.rc4.4.fc14.x86_64 #1
Call Trace:
 [&lt;ffffffff8104e27b&gt;] warn_slowpath_common+0x85/0x9d
 [&lt;ffffffffa02782e0&gt;] ? iwl4965_show_temperature+0x49/0x49 [iwl4965]
 [&lt;ffffffff8104e336&gt;] warn_slowpath_fmt+0x46/0x48
 [&lt;ffffffffa027712f&gt;] iwl4965_send_tx_power+0x61/0x102 [iwl4965]
 [&lt;ffffffff81477e05&gt;] ? mutex_lock+0x36/0x50
 [&lt;ffffffffa0278337&gt;] iwl4965_bg_txpower_work+0x57/0x73 [iwl4965]
 [&lt;ffffffff810647f3&gt;] process_one_work+0x18d/0x286
 [&lt;ffffffff81065a5e&gt;] worker_thread+0xfd/0x181
 [&lt;ffffffff81065961&gt;] ? manage_workers.clone.16+0x172/0x172
 [&lt;ffffffff81069036&gt;] kthread+0x82/0x8a
 [&lt;ffffffff81480524&gt;] kernel_thread_helper+0x4/0x10
 [&lt;ffffffff81068fb4&gt;] ? kthread_worker_fn+0x14b/0x14b
 [&lt;ffffffff81480520&gt;] ? gs_change+0x13/0x13

Reported-and-tested-by: Paul Bolle &lt;pebolle@tiscali.nl&gt;
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>iwlegacy: led stay solid on when no traffic</title>
<updated>2011-04-28T18:38:35+00:00</updated>
<author>
<name>Wey-Yi Guy</name>
<email>wey-yi.w.guy@intel.com</email>
</author>
<published>2011-04-25T18:12:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=1501b6764f0c363a9f1d72f9d422841f81f1bd8c'/>
<id>1501b6764f0c363a9f1d72f9d422841f81f1bd8c</id>
<content type='text'>
commit 5ed540aecc2aae92d5c97b9a9306a5bf88ad5574 change the led behavior
for iwlwifi driver; the side effect cause led blink all the time.

Modify the led blink table to fix this problem

Signed-off-by: Wey-Yi Guy &lt;wey-yi.w.guy@intel.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit 5ed540aecc2aae92d5c97b9a9306a5bf88ad5574 change the led behavior
for iwlwifi driver; the side effect cause led blink all the time.

Modify the led blink table to fix this problem

Signed-off-by: Wey-Yi Guy &lt;wey-yi.w.guy@intel.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>b43: trivial: update module info about ucode16_mimo firmware</title>
<updated>2011-04-28T18:38:35+00:00</updated>
<author>
<name>Rafał Miłecki</name>
<email>zajec5@gmail.com</email>
</author>
<published>2011-04-19T20:49:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=f61583941667c96d61fc6991b9f23307f9bfa87e'/>
<id>f61583941667c96d61fc6991b9f23307f9bfa87e</id>
<content type='text'>
Signed-off-by: Rafał Miłecki &lt;zajec5@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Signed-off-by: Rafał Miłecki &lt;zajec5@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
