<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/net/wireless/b43, branch linux-2.6.27.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.27.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.27.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2009-11-10T00:51:53Z</updated>
<entry>
<title>b43: Fix Bugzilla #14181 and the bug from the previous 'fix'</title>
<updated>2009-11-10T00:51:53Z</updated>
<author>
<name>Larry Finger</name>
</author>
<published>2009-10-16T15:18:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9a3e3d7cf51eeafaad9f90c7c1d8f0b97ed0687e'/>
<id>urn:sha1:9a3e3d7cf51eeafaad9f90c7c1d8f0b97ed0687e</id>
<content type='text'>
commit d50bae33d1358b909ade05ae121d83d3a60ab63f upstream.

"b43: Fix PPC crash in rfkill polling on unload" fixed the bug reported
in Bugzilla No. 14181; however, it introduced a new bug. Whenever the
radio switch was turned off, it was necessary to unload and reload
the driver for it to recognize the switch again.

This patch fixes both the original bug in #14181 and the bug introduced by
the previous patch. It must be stated, however, that if there is a BCM4306/3
with an rfkill switch (not yet proven), then the driver will need an
unload/reload cycle to turn the device back on.

Signed-off-by: Larry Finger &lt;Larry.Finger@lwfinger.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>b43: Refresh RX poison on buffer recycling</title>
<updated>2009-05-08T21:54:34Z</updated>
<author>
<name>Michael Buesch</name>
</author>
<published>2009-04-24T16:05:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ac37ac5e637cbf7b2f77cd89c9396ef3a569adf3'/>
<id>urn:sha1:ac37ac5e637cbf7b2f77cd89c9396ef3a569adf3</id>
<content type='text'>
upstream commit: cf68636a9773aa97915497fe54fa4a51e3f08f3a

The RX buffer poison needs to be refreshed, if we recycle an RX buffer,
because it might be (partially) overwritten by some DMA operations.

Cc: stable@kernel.org
Cc: Francesco Gringoli &lt;francesco.gringoli@ing.unibs.it&gt;
Signed-off-by: Michael Buesch &lt;mb@bu3sch.de&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>b43: Poison RX buffers</title>
<updated>2009-05-08T21:54:34Z</updated>
<author>
<name>Michael Buesch</name>
</author>
<published>2009-04-24T16:05:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=89718ae496e551c625560eb2b54fa606d50ca945'/>
<id>urn:sha1:89718ae496e551c625560eb2b54fa606d50ca945</id>
<content type='text'>
upstream commit: ec9a1d8c13e36440eda0f3c79b8149080e3ab5ba

This patch adds poisoning and sanity checking to the RX DMA buffers.
This is used for protection against buggy hardware/firmware that raises
RX interrupts without doing an actual DMA transfer.

This mechanism protects against rare "bad packets" (due to uninitialized skb data)
and rare kernel crashes due to uninitialized RX headers.

The poison is selected to not match on valid frames and to be cheap for checking.

The poison check mechanism _might_ trigger incorrectly, if we are voluntarily
receiving frames with bad PLCP headers. However, this is nonfatal, because the
chance of such a match is basically zero and in case it happens it just results
in dropping the packet.
Bad-PLCP RX defaults to off, and you should leave it off unless you want to listen
to the latest news broadcasted by your microwave oven.

This patch also moves the initialization of the RX-header "length" field in front of
the mapping of the DMA buffer. The CPU should not touch the buffer after we mapped it.

Cc: stable@kernel.org
Reported-by: Francesco Gringoli &lt;francesco.gringoli@ing.unibs.it&gt;
Signed-off-by: Michael Buesch &lt;mb@bu3sch.de&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>b43: fix b43_plcp_get_bitrate_idx_ofdm return type</title>
<updated>2009-05-02T17:23:33Z</updated>
<author>
<name>Lorenzo Nava</name>
</author>
<published>2009-03-28T01:45:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b35d63e5d76dae5b1c5f796a78df6e8fc2b76850'/>
<id>urn:sha1:b35d63e5d76dae5b1c5f796a78df6e8fc2b76850</id>
<content type='text'>
upstream commit: a3c0b87c4f21911fb7185902dd13f0e3cd7f33f7

This patch fixes the return type of b43_plcp_get_bitrate_idx_ofdm. If
the plcp contains an error, the function return value is 255 instead
of -1, and the packet was not dropped. This causes a warning in
__ieee80211_rx function because rate idx is out of range.

Cc: stable@kernel.org
Signed-off-by: Lorenzo Nava &lt;navalorenx@gmail.com&gt;
Signed-off-by: Michael Buesch &lt;mb@bu3sch.de&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>Revert "b43/b43legacy: add RFKILL_STATE_HARD_BLOCKED support"</title>
<updated>2008-09-17T02:32:30Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2008-09-17T02:32:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e95926d05d028a6bf0ab60b21b484c3d622fdcd1'/>
<id>urn:sha1:e95926d05d028a6bf0ab60b21b484c3d622fdcd1</id>
<content type='text'>
This reverts commit bc19d6e0b74ef03a3baf035412c95192b54dfc6f, which as
Larry Finger reports causes the radio LED on his system to no longer
respond to rfkill switch events.

Reported-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Requested-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>removed unused #include &lt;version.h&gt;</title>
<updated>2008-08-18T15:05:15Z</updated>
<author>
<name>Huang Weiyi</name>
</author>
<published>2008-08-16T23:50:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3eb75aac8907e7ea36f0d078b2cc7393986001cf'/>
<id>urn:sha1:3eb75aac8907e7ea36f0d078b2cc7393986001cf</id>
<content type='text'>
The drivers below do not use LINUX_VERSION_CODE nor KERNEL_VERSION.
  drivers/net/wireless/ath5k/base.c
  drivers/net/wireless/b43/main.c
  drivers/net/wireless/ipw2100.c
  drivers/net/wireless/ipw2200.c
  drivers/net/wireless/iwlwifi/iwl-3945.c
  drivers/net/wireless/iwlwifi/iwl-4965.c
  drivers/net/wireless/iwlwifi/iwl-5000.c
  drivers/net/wireless/iwlwifi/iwl-agn.c
  drivers/net/wireless/iwlwifi/iwl-core.c
  drivers/net/wireless/iwlwifi/iwl-eeprom.c
  drivers/net/wireless/iwlwifi/iwl-hcmd.c
  drivers/net/wireless/iwlwifi/iwl-power.c
  drivers/net/wireless/iwlwifi/iwl3945-base.c

This patch removes the said #include &lt;version.h&gt;.

Signed-off-by: Huang Weiyi &lt;weiyi.huang@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>b43: Fix for another Bluetooth Coexistence SPROM Programming error for BCM4306</title>
<updated>2008-08-18T15:05:15Z</updated>
<author>
<name>Larry Finger</name>
</author>
<published>2008-08-14T23:57:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=430cd47fa98178b5199105fab4fb74e04bd0635c'/>
<id>urn:sha1:430cd47fa98178b5199105fab4fb74e04bd0635c</id>
<content type='text'>
In trying to help users on the Ubuntu Bugzilla, I discovered another
BCM4306 with the Bluetooth Coexistence programming error in the SPROM.

This patch is contingent on the one that added the Linksys device with
subdevice code of 0x0014.

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>b43: Fix for SPROM coding error in Linksys WMP54G (BCM4306/3)</title>
<updated>2008-08-18T15:05:13Z</updated>
<author>
<name>Larry Finger</name>
</author>
<published>2008-08-10T15:19:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a58d452290aafae30b021c8bf185853b1aaf2092'/>
<id>urn:sha1:a58d452290aafae30b021c8bf185853b1aaf2092</id>
<content type='text'>
The Linksys WMP54G (BCM4306/3) card in a PCI format has an SPROM coding
error and needs the fix found for several other cards.

Signed-off-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Cc: Stable &lt;stable@kernel.org&gt;		[2.6.25.x, 2.6.26.x]
Signed-off-by: Michael Buesch &lt;mb@bu3sch.de&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>mac80211: partially fix skb-&gt;cb use</title>
<updated>2008-07-29T20:55:08Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2008-07-29T09:32:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d0f09804144fd9471a13cf4d80e66842c7fa114f'/>
<id>urn:sha1:d0f09804144fd9471a13cf4d80e66842c7fa114f</id>
<content type='text'>
This patch fixes mac80211 to not use the skb-&gt;cb over the queue step
from virtual interfaces to the master. The patch also, for now,
disables aggregation because that would still require requeuing,
will fix that in a separate patch. There are two other places (software
requeue and powersaving stations) where requeue can happen, but that is
not currently used by any drivers/not possible to use respectively.

Signed-off-by: Johannes Berg &lt;johannes@sipsolutions.net&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>mac80211: remove IEEE80211_HW_HOST_GEN_BEACON_TEMPLATE flag</title>
<updated>2008-07-29T20:36:24Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2008-07-15T08:10:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=605a0bd66d9d55e9ba46da1a9e5140c68bdf6d85'/>
<id>urn:sha1:605a0bd66d9d55e9ba46da1a9e5140c68bdf6d85</id>
<content type='text'>
I forgot this in the previous patch that made it unused.

Signed-off-by: Johannes Berg &lt;johannes@sipsolutions.net&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
</feed>
