From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <larry.finger@lwfinger.net>
Cc: John Linville <linville@tuxdriver.com>,
Bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] b43: Changes to enable BCM4311 rev 02 with wireless core revision 13
Date: Wed, 21 Nov 2007 21:10:15 +0100 [thread overview]
Message-ID: <200711212110.15901.mb@bu3sch.de> (raw)
In-Reply-To: <47448ED1.9090100@lwfinger.net>
On Wednesday 21 November 2007 21:02:25 Larry Finger wrote:
> Michael Buesch wrote:
> > On Wednesday 21 November 2007 20:31:53 Larry Finger wrote:
> >> The BCM94311MCG rev 02 chip has an 802.11 core with revision 13 an=
d
> >> has not been supported until now. The changes include the followin=
g:
> >>
> >> (1) Add the 802.11 rev 13 device to the ssb_device_id table to loa=
d b43.
> >> (2) Add PHY revision 9 to the supported list.
> >> (3) Fix 64-bit addressing errors.
> >> (4) Remove some magic numbers in the DMA setup.
> >>
> >> The DMA implementation for this chip supports full 64-bit addressi=
ng with
> >> one exception. Whenever the Descriptor Ring Buffer is in high memo=
ry, 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". Whe=
n
> >> 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. The presen=
t driver
> >> allocates one ring buffer for RX and six for TX; however, only one=
of the
> >> TX buffers is used. To minimize any system impact associated with =
using low
> >> memory, this patch removes the allocation of the unused buffers.
> >>
> >> This patch has been tested by C=C3=A9dric Caumont <icare40@hotmail=
=2Ecom>.
> >>
> >=20
> >> @@ -954,19 +955,21 @@ int b43_dma_init(struct b43_wldev *dev)
> >> =20
> >> err =3D -ENOMEM;
> >> /* setup TX DMA channels. */
> >> - ring =3D b43_setup_dmaring(dev, 0, 1, dma64);
> >> + ring =3D b43_setup_dmaring(dev, 1, 1, dma64);
> >> if (!ring)
> >> goto out;
> >> - dma->tx_ring0 =3D ring;
> >> + dma->tx_ring1 =3D ring;
> >> =20
> >> - ring =3D b43_setup_dmaring(dev, 1, 1, dma64);
> >> + /* The driver only uses ring1 for TX - skip setup for the rest *=
/
> >> +#if 0
> >=20
> > NACK.
>=20
> Are you NACKing the "if 0" or the elimination of the unused TX rings?=
Perhaps we could have
Both
> if (ring->dma64)
> goto out;
No,
I am going to submit patches to enable use of multiple TX queues.
See my quilt series.
Simply don't change current behaviour. ;)
The only reason for me holding these patches back is that I could
not sufficiently test them yet.
--=20
Greetings Michael.
-
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-11-21 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 19:31 [PATCH] b43: Changes to enable BCM4311 rev 02 with wireless core revision 13 Larry Finger
2007-11-21 19:44 ` Michael Buesch
2007-11-21 20:02 ` Larry Finger
2007-11-21 20:10 ` Michael Buesch [this message]
2007-11-21 21:33 ` Chuck Ebbert
2007-11-21 21:49 ` Larry Finger
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=200711212110.15901.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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.