From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:39735 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933590AbYCABT0 (ORCPT ); Fri, 29 Feb 2008 20:19:26 -0500 Date: Fri, 29 Feb 2008 16:29:19 -0800 From: Greg KH To: Michael Buesch Cc: stable@kernel.org, bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org, Alexey Zaytsev Subject: Re: [PATCH stable] b43: Backport bcm4311 fix Message-ID: <20080301002919.GA17761@kroah.com> (sfid-20080301_012004_777084_34FE65E8) References: <200802291255.41906.mb@bu3sch.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <200802291255.41906.mb@bu3sch.de> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Fri, Feb 29, 2008 at 12:55:41PM +0100, Michael Buesch wrote: > The changes include the following: > > (1) Add the 802.11 rev 13 device to the ssb_device_id table to load b43. > (2) Add PHY revision 9 to the supported list. > (3) Change the 2-bit routing code for address extensions to 0b10 rather > than the 0b01 used for the 32-bit case. > (4) Remove some magic numbers in the DMA setup. > > The DMA implementation for this chip supports full 64-bit addressing with > one exception. Whenever the Descriptor Ring Buffer is in high memory, a > fatal DMA error occurs. This problem was not present in 2.6.24-rc2 due > to code to "Bias the placement of kernel pages at lower PFNs". When > commit 44048d70 reverted that code, the DMA error appeared. As a "fix", > use the GFP_DMA flag when allocating the buffer for 64-bit DMA. At present, > this problem is thought to arise from a hardware error. Is this logic upstream in 2.6.25-rcX already? If so, do you have a git id for it so that I can match them up? thanks, greg k-h