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

On 05/24/2012 03:25 PM, 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.
> To increase the robustness, change the end of the for loop from "i < 10"
> to "i < 5000". I could never do that in final code as it would delay
> forever if the firmware were really missing, but it will delay long
> enough to handle an fsck on root, your entering of the password for the
> encrypted fs, or whatever slows the starting of userland.

Is there no event that you can use to determine when user-space is
available? In the original udev discussion it was suggested to use
IFF_UP, but I did not find anyone saying what the equivalent mac80211
callback should be.

Also this issue can occur when the firmware is only available on the
real root, but the ramdisk contains the b43 module.

Gr. AvS


  parent reply	other threads:[~2012-05-24 16:44 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
2012-05-24 16:43       ` Arend van Spriel [this message]
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=4FBE654C.2040206@broadcom.com \
    --to=arend@broadcom.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=bugs-wireless@aquazul.com \
    --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).