From: Michael Buesch <mb@bu3sch.de>
To: gavron@wetwork.net
Cc: linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: [PATCH RFT] b43: We need lots of regression testing
Date: Fri, 4 Apr 2008 22:02:39 +0200 [thread overview]
Message-ID: <200804042202.39854.mb@bu3sch.de> (raw)
In-Reply-To: <47F68931.4040205@wetwork.net>
On Friday 04 April 2008 22:01:53 gavron@wetwork.net wrote:
> Works great on my 4311 rev 01.
Thanks a lot for testing!
> Michael Buesch wrote:
> > Hi b43 users,
> >
> > Please be so kind to run lots of regression tests on the following
> > patch. This patch is supposed to make the LO calibration a _lot_ more
> > lightweight and avoid a long MAC-disable period every 120 seconds.
> >
> > We need a lot of regression testing with this patch on lots of different
> > devices to make sure we don't introduce regressions.
> >
> > I tested this on a 4306 and a 4318 card. So far it seems to work great
> > on these cards.
> >
> > Thanks.
> >
> >
> > ---------- Forwarded Message ----------
> >
> > Subject: Re: b43: 1 second "freeze" every 2 minutes - works with bcm43xx
> > Date: Friday 04 April 2008
> > From: Michael Buesch <mb@bu3sch.de>
> >
> > Can you try the following patch?
> > http://bu3sch.de/patches/wireless-testing/20080404-1408/patches/010-b43-calibrate-lo-on-demand.patch
> >
> > This patch is supposed to distribute the calibration bursts over time,
> > so that calibration only happens when it's actually needed.
> > So instead of disabling the MAC every 120 secs and recalibrating the
> > whole calibration tables, we assign a timeout to each calibration value
> > and only recalibrate it if it's
> > a) expired and
> > b) currently used.
> > Recalibration might also happen on TX power adjustment, if the corresponding
> > calibration item is no longer in the cache because it has expired. That
> > actually happens most of the time, but we can live with it, as power adjustment
> > doesn't happen that often and calibration is a _lot_ cheaper.
> >
> > This patch also reduced overall memory consumption by nuking the
> > huge static calibration tables.
> >
> > Disclaimer:
> > The algorithms in this patch are completely redesigned and have nothing in
> > common with how broadcom does the stuff in the proprietary driver. So it's
> > highly experimental and I'm not responsible in case this patch eats your cat.
> >
> > -------------------------------------------------------
--
Greetings Michael.
next prev parent reply other threads:[~2008-04-04 20:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 14:12 [PATCH RFT] b43: We need lots of regression testing Michael Buesch
2008-04-04 20:01 ` gavron
2008-04-04 20:02 ` Michael Buesch [this message]
2008-04-05 3:06 ` Pavel Roskin
2008-04-05 9:09 ` Johannes Berg
2008-04-06 5:12 ` Pavel Roskin
2008-04-05 10:48 ` gavron
2008-04-06 5:46 ` Pavel Roskin
-- strict thread matches above, loose matches on Subject: below --
2008-04-06 8:23 Ronald
2008-04-07 1:26 ` Pavel Roskin
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=200804042202.39854.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=gavron@wetwork.net \
--cc=linux-wireless@vger.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.