<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/net/wireless, branch v3.1</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/net/wireless?h=v3.1</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/net/wireless?h=v3.1'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2011-09-27T19:47:33Z</updated>
<entry>
<title>Merge branch 'master' of git://git.infradead.org/users/linville/wireless into for-davem</title>
<updated>2011-09-27T19:47:33Z</updated>
<author>
<name>John W. Linville</name>
<email>linville@tuxdriver.com</email>
</author>
<published>2011-09-27T19:47:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a8acfd82ebefbb32f12f413019e53f9e939cf44e'/>
<id>urn:sha1:a8acfd82ebefbb32f12f413019e53f9e939cf44e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ath9k: Fix a dma warning/memory leak</title>
<updated>2011-09-26T18:55:51Z</updated>
<author>
<name>Mohammed Shafi Shajakhan</name>
<email>mohammed@qca.qualcomm.com</email>
</author>
<published>2011-09-23T09:03:14Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ba54238552625aad2d75f455a4d3db18ea7dec68'/>
<id>urn:sha1:ba54238552625aad2d75f455a4d3db18ea7dec68</id>
<content type='text'>
proper dma_unmapping and freeing of skb's has to be done in the rx
cleanup for EDMA chipsets when the device is unloaded and this also
seems to address the following warning which shows up occasionally when
the device is unloaded

	Call Trace:
	[&lt;c0148cd2&gt;] warn_slowpath_common+0x72/0xa0
	[&lt;c03b669c&gt;] ? dma_debug_device_change+0x19c/0x200
	[&lt;c03b669c&gt;] ? dma_debug_device_change+0x19c/0x200
	[&lt;c0148da3&gt;] warn_slowpath_fmt+0x33/0x40
	[&lt;c03b669c&gt;] dma_debug_device_change+0x19c/0x200
	[&lt;c0657f12&gt;] notifier_call_chain+0x82/0xb0
	[&lt;c0171370&gt;] __blocking_notifier_call_chain+0x60/0x90
	[&lt;c01713bf&gt;] blocking_notifier_call_chain+0x1f/0x30
	[&lt;c044f594&gt;] __device_release_driver+0xa4/0xc0
	[&lt;c044f647&gt;] driver_detach+0x97/0xa0
	[&lt;c044e65c&gt;] bus_remove_driver+0x6c/0xe0
	[&lt;c029af0b&gt;] ? sysfs_addrm_finish+0x4b/0x60
	[&lt;c0450109&gt;] driver_unregister+0x49/0x80
	[&lt;c0299f54&gt;] ? sysfs_remove_file+0x14/0x20
	[&lt;c03c3ab2&gt;] pci_unregister_driver+0x32/0x80
	[&lt;f92c2162&gt;] ath_pci_exit+0x12/0x20 [ath9k]
	[&lt;f92c8467&gt;] ath9k_exit+0x17/0x36 [ath9k]
	[&lt;c06523cd&gt;] ? mutex_unlock+0xd/0x10
	[&lt;c018e27f&gt;] sys_delete_module+0x13f/0x200
	[&lt;c02139bb&gt;] ? sys_munmap+0x4b/0x60
	[&lt;c06547c5&gt;] ? restore_all+0xf/0xf
	[&lt;c0657a20&gt;] ? spurious_fault+0xe0/0xe0
	[&lt;c01832f4&gt;] ? trace_hardirqs_on_caller+0xf4/0x180
	[&lt;c065b863&gt;] sysenter_do_call+0x12/0x38
	 ---[ end trace 16e1c1521c06bcf9 ]---
	Mapped at:
	[&lt;c03b7938&gt;] debug_dma_map_page+0x48/0x120
	[&lt;f92ba3e8&gt;] ath_rx_init+0x3f8/0x4b0 [ath9k]
	[&lt;f92b5ae4&gt;] ath9k_init_device+0x4c4/0x7b0 [ath9k]
	[&lt;f92c2813&gt;] ath_pci_probe+0x263/0x330 [ath9k]

Signed-off-by: Mohammed Shafi Shajakhan &lt;mohammed@qca.qualcomm.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>rtlwifi: rtl8192cu: Fix unitialized struct</title>
<updated>2011-09-26T18:55:50Z</updated>
<author>
<name>Larry Finger</name>
<email>Larry.Finger@lwfinger.net</email>
</author>
<published>2011-09-23T03:59:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=831d85471e761e190c3c8979b37540d699ae5812'/>
<id>urn:sha1:831d85471e761e190c3c8979b37540d699ae5812</id>
<content type='text'>
Driver rtl8192cu assigns a new struct rtl_tcb_desc object, but fails to
clear it.

Signed-off-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Cc: Stable &lt;stable@kernel.org&gt;  [2.6.39+]
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>iwlagn: fix dangling scan request</title>
<updated>2011-09-26T18:55:50Z</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2011-09-22T21:59:04Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6c80c39d9a6986a566c30d797aae37bfb697eea3'/>
<id>urn:sha1:6c80c39d9a6986a566c30d797aae37bfb697eea3</id>
<content type='text'>
If iwl_scan_initiate() fails for any reason,
priv-&gt;scan_request and priv-&gt;scan_vif are left
dangling. This can lead to a crash later when
iwl_bg_scan_completed() tries to run a pending
scan request.

In practice, this seems to be very rare due to
the STATUS_SCANNING check earlier. That check,
however, is wrong -- it should allow a scan to
be queued when a reset/roc scan is going on.
When a normal scan is already going on, a new
one can't be issued by mac80211, so that code
can be removed completely. I introduced this
bug when adding off-channel support in commit
266af4c745952e9bebf687dd68af58df553cb59d.

Cc: stable@kernel.org [3.0]
Reported-by: Peng Yan &lt;peng.yan@intel.com&gt;
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
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>
</entry>
<entry>
<title>iwlegacy: do not use interruptible waits</title>
<updated>2011-09-21T19:58:24Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2011-09-20T14:49:03Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=65d0f19e583e80e42b1c67c166bfc4dfdf6ab693'/>
<id>urn:sha1:65d0f19e583e80e42b1c67c166bfc4dfdf6ab693</id>
<content type='text'>
iwlegacy version of fix:

commit effd4d9aece9184f526e6556786a94d335e38b71
Author: Johannes Berg &lt;johannes.berg@intel.com&gt;
Date:   Thu Sep 15 11:46:52 2011 -0700

    iwlagn: do not use interruptible waits

    Since the dawn of its time, iwlwifi has used
    interruptible waits to wait for synchronous
    commands and firmware loading.

    This leads to "interesting" bugs, because it
    can't actually handle the interruptions; for
    example when a command sending is interrupted
    it will assume the command completed fully,
    and then leave it pending, which leads to all
    kinds of trouble when the command finishes
    later.

    Since there's no easy way to gracefully deal
    with interruptions, fix the driver to not use
    interruptible waits.

    This at least fixes the error
    iwlagn 0000:02:00.0: Error: Response NULL in  'REPLY_SCAN_ABORT_CMD'

    I have seen in P2P testing, but it is likely
    that there are other errors caused by this.

Cc: stable@kernel.org # 2.6.39+
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>iwlegacy: fix command queue timeout</title>
<updated>2011-09-21T19:58:23Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2011-09-20T14:46:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2e2a41d6ca07d1b2aa67015c35fd80701c98e867'/>
<id>urn:sha1:2e2a41d6ca07d1b2aa67015c35fd80701c98e867</id>
<content type='text'>
iwlegacy version of fix:

commit 282cdb325aea4ebbc42ce753b47cc96145eb54bc
Author: Johannes Berg &lt;johannes.berg@intel.com&gt;
Date:   Mon Sep 12 12:09:10 2011 -0700

    iwlagn: fix command queue timeout

    If the command queue is constantly busy,
    which can happen in P2P, the hangcheck
    timer will frequently find a command in
    it and will eventually reset the device
    because nothing sets the timestamp for
    this queue when commands are processed.

    Fix this by setting the timestamp when
    a command completes.

iwlegacy does not support P2P, but this patch fix possible
unneeded hardware resets, hence is needed.

Cc: stable@kernel.org  # 2.6.39+
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>ath9k_hw: Fix Rx DMA stuck for AR9003 chips</title>
<updated>2011-09-21T19:58:22Z</updated>
<author>
<name>Rajkumar Manoharan</name>
<email>rmanohar@qca.qualcomm.com</email>
</author>
<published>2011-09-20T10:53:51Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e9f9530bb697f53dd620df290102359a3325bb23'/>
<id>urn:sha1:e9f9530bb697f53dd620df290102359a3325bb23</id>
<content type='text'>
During the endurance testing, rx frames are not getting DMAd from
MAC whereas pcu rx frame counters are getting updated properly.
As per systems team input updated the initval to fix rx dma stuck
issue.

Cc: stable@kernel.org
Signed-off-by: Rajkumar Manoharan &lt;rmanohar@qca.qualcomm.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'master' of ssh://infradead/~/public_git/wireless into for-davem</title>
<updated>2011-09-20T13:19:14Z</updated>
<author>
<name>John W. Linville</name>
<email>linville@tuxdriver.com</email>
</author>
<published>2011-09-20T13:19:14Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=eebb6fb4ae2f60a82e38afb6d8b373a4216bf891'/>
<id>urn:sha1:eebb6fb4ae2f60a82e38afb6d8b373a4216bf891</id>
<content type='text'>
</content>
</entry>
<entry>
<title>b43: Fix beacon problem in ad-hoc mode</title>
<updated>2011-09-19T18:51:51Z</updated>
<author>
<name>Manual Munz</name>
<email>freifunk@somakoma.de</email>
</author>
<published>2011-09-18T23:24:03Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8c23516fbb209ccf8f8c36268311c721faff29ee'/>
<id>urn:sha1:8c23516fbb209ccf8f8c36268311c721faff29ee</id>
<content type='text'>
In ad-hoc mode, driver b43 does not issue beacons.

Signed-off-by: Manual Munz &lt;freifunk@somakoma.de&gt;
Tested-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Signed-off-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Cc: Stable &lt;stable@kernel.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>iwlagn: workaround bug crashing some APs</title>
<updated>2011-09-16T19:32:12Z</updated>
<author>
<name>Don Fry</name>
<email>donald.h.fry@intel.com</email>
</author>
<published>2011-09-15T15:36:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2249b011432ca3dcce112f0f71e0f531b4bb9347'/>
<id>urn:sha1:2249b011432ca3dcce112f0f71e0f531b4bb9347</id>
<content type='text'>
This patch reverts commit 9b7688328422b88a7a15dc0dc123ad9ab1a6e22d which
was introduced in 2.6.38-rc1.  It works around a problem where the iwlagn
driver stimulates a bug crashing (requiring power cycle to recover) some
APs under heavy traffic.

CC: stable@kernel.org #2.6.39, #3.0.0 #3.1.0
Signed-off-by: Don Fry &lt;donald.h.fry@intel.com&gt;
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>
</entry>
</feed>
