linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mourad De Clerck <bugs-wireless@aquazul.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: firmware loading fails for b43 using linux 3.4?
Date: Thu, 24 May 2012 18:41:36 +0200	[thread overview]
Message-ID: <4FBE64C0.8000804@aquazul.com> (raw)
In-Reply-To: <4FBE36B8.8020208@lwfinger.net>

On 24/05/12 15:25, Larry Finger wrote:
> It may be a while before I sort out all the details of this fix. Until
> then, you can use either the temporary fix or compile b43 as a module.

Yes, no worries – I'm perfectly happy with the workaround of using b43 
as a module. I just wanted to follow through with it.

> I always have the wireless drivers built as modules. When making
> changes, one only needs to recompile, reinstall the new version, and
> unload/reload the module. If built into the kernel, a reboot is needed
> for every change. None the less, the code needs to handle all cases.

Yes, I figured as much… but that's why there's testers after all :)

In any case, thank you for your work on this…

Kind regards,

-- Mourad

  reply	other threads:[~2012-05-24 16:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 23:49 firmware loading fails for b43 using linux 3.4? Mourad De Clerck
2012-05-24  1:13 ` Larry Finger
2012-05-24  2:44   ` Mourad De Clerck
2012-05-24  3:03 ` Larry Finger
2012-05-24  4:38   ` Mourad De Clerck
2012-05-24 13:25     ` Larry Finger
2012-05-24 16:41       ` Mourad De Clerck [this message]
2012-05-24 16:43       ` Arend van Spriel
2012-05-24 19:36         ` 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=4FBE64C0.8000804@aquazul.com \
    --to=bugs-wireless@aquazul.com \
    --cc=Larry.Finger@lwfinger.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 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).