From: Michael Buesch <mb@bu3sch.de>
To: Francesco Gringoli <francesco.gringoli@ing.unibs.it>
Cc: linville@tuxdriver.com, bcm43xx-dev@lists.berlios.de,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] b43: Refresh RX poison on buffer recycling
Date: Mon, 30 Mar 2009 23:50:58 +0200 [thread overview]
Message-ID: <200903302350.58971.mb@bu3sch.de> (raw)
In-Reply-To: <C0D59D9C-FC8A-4C79-B777-AF2F166D9711@ing.unibs.it>
On Monday 30 March 2009 23:35:34 Francesco Gringoli wrote:
> I have one more question: the hardware seems to allow frames that are
> longer than 2352 bytes. If we monitor the firmware during receiving we
> get up to 0x1005 bytes long frames. When such frames arrives, the
> kernel drops them as the "The data did not fit into one descriptor
> buffer and is split over multiple buffers." I tried to increase
> B43_DMA0_RX_BUFFERSIZE up to 0x1006 but I get problems with dma and
> the driver keeps restarting the hardware forever. What is wrong with
> increasing this value above IEEE80211_MAX_FRAME_LEN?
Well... First thing is that I think the hardware wasn't ever
tested with frames >IEEE80211_MAX_FRAME_LEN. So there might be silicon bugs.
The maximum number of bytes one descriptor can carry is 8191 bytes (not including
RX headers and padding. That's 30 bytes).
Third thing is that the buffer must not cross a page boundary. So that is
4096 bytes on most machines. So in practice the 4096 bytes boundary (minus 30 bytes
for headers/padding) is upper bound for B43_DMA0_RX_BUFFERSIZE.
--
Greetings, Michael.
prev parent reply other threads:[~2009-03-30 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 23:41 [PATCH] b43: Refresh RX poison on buffer recycling Michael Buesch
2009-03-30 21:35 ` Francesco Gringoli
2009-03-30 21:50 ` Michael Buesch [this message]
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=200903302350.58971.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=francesco.gringoli@ing.unibs.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).