All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: stable@kernel.org, bcm43xx-dev@lists.berlios.de,
	linux-wireless@vger.kernel.org,
	Alexey Zaytsev <alexey.zaytsev@gmail.com>
Subject: Re: [PATCH stable] b43: Backport bcm4311 fix
Date: Fri, 29 Feb 2008 16:29:19 -0800	[thread overview]
Message-ID: <20080301002919.GA17761@kroah.com> (raw)
In-Reply-To: <200802291255.41906.mb@bu3sch.de>

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

  reply	other threads:[~2008-03-01  1:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 11:55 [PATCH stable] b43: Backport bcm4311 fix Michael Buesch
2008-03-01  0:29 ` Greg KH [this message]
2008-03-01  1:39   ` Alexey Zaytsev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080301002919.GA17761@kroah.com \
    --to=greg@kroah.com \
    --cc=alexey.zaytsev@gmail.com \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=stable@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.