From: "Gábor Stefanik" <netrolller.3d@gmail.com>
To: Michael Buesch <mb@bu3sch.de>, Larry Finger <Larry.Finger@lwfinger.net>
Cc: bcm43xx-dev@lists.berlios.de,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH RESEND] b43: implement baseband init for LP-PHY <= rev1
Date: Mon, 3 Aug 2009 23:34:09 +0200 [thread overview]
Message-ID: <69e28c910908031434q53fd7d6jb346f49927a634a7@mail.gmail.com> (raw)
In-Reply-To: <200908032316.30237.mb@bu3sch.de>
On Mon, Aug 3, 2009 at 11:16 PM, Michael Buesch<mb@bu3sch.de> wrote:
> On Monday 03 August 2009 22:58:30 Larry Finger wrote:
>> Gábor states it the way the Broadcom routine is written. They have the
>> flags divided into 3 16-bit values - high, middle, and low. The values
>> are kept in arrays - one set is for the current band and the other is
>> for both bands. When the routine is entered, the appropriate quantity
>> is saved in a temporary, then the array value is maskset. Only when
>> the resulting value changes is the shared memory location updated. The
>> implication is that shared memory writes are expensive. Is that true?
>
> No. I think it has other reasons.
>
> --
> Greetings, Michael.
>
In that case, is the code correct:
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
prev parent reply other threads:[~2009-08-03 21:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 22:18 [PATCH RESEND] b43: implement baseband init for LP-PHY <= rev1 Gábor Stefanik
2009-08-02 22:24 ` Gábor Stefanik
2009-08-02 22:35 ` Michael Buesch
2009-08-03 9:13 ` Michael Buesch
2009-08-03 9:15 ` Michael Buesch
2009-08-03 13:55 ` Gábor Stefanik
2009-08-03 20:38 ` Michael Buesch
2009-08-03 20:41 ` Gábor Stefanik
2009-08-03 20:58 ` Larry Finger
2009-08-03 21:16 ` Michael Buesch
2009-08-03 21:34 ` Gábor Stefanik [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=69e28c910908031434q53fd7d6jb346f49927a634a7@mail.gmail.com \
--to=netrolller.3d@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).