linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Stefano Brivio <stefano.brivio@polimi.it>
Cc: John Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: b43legacy: fix MAC control and microcode init
Date: Wed, 23 Jan 2008 15:14:20 +0100	[thread overview]
Message-ID: <200801231514.21045.mb@bu3sch.de> (raw)
In-Reply-To: <20080123144850.19a0545b@morte>

On Wednesday 23 January 2008 14:48:50 Stefano Brivio wrote:
> This zeros out all microcode related memory before loading
> the microcode.
> 
> This also fixes initialization of the MAC control register.
> The _only_ place where we overwrite the contents of the MAC control
> register is at the beginning of b43_chip_init().
> All other places must do read() -> mask/set -> write() to not
> overwrite existing bits.
> 
> This also adds a longer delay for waiting for the microcode
> to initialize itself. It seems that the current timeout is sufficient
> on all available devices, but there's no real reason why we shouldn't
> wait for up to one second. Slow embedded devices might exist.
> Better safe than sorry.
> 
> While at it, fix naming of MACCTL values.
> 
> This patch by Michael Buesch has been ported to b43legacy.
> 
> Cc: Michael Buesch <mb@bu3sch.de>
> Signed-off-by: Stefano Brivio <stefano.brivio@polimi.it>
> ---

Acked-by: Michael Buesch <mb@bu3sch.de>

> John, this bugfix should go into 2.6.24, if possible.

We agreed in private that this is actually pretty intrusive and
the patches should _not_ go into 2.6.24, as they don't actually
fix known bugs.

-- 
Greetings Michael.

      reply	other threads:[~2008-01-23 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23 13:48 b43legacy: fix MAC control and microcode init Stefano Brivio
2008-01-23 14:14 ` 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=200801231514.21045.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=stefano.brivio@polimi.it \
    /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).