b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Felix Janda <felix.janda@posteo.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: John W Linville <linville@tuxdriver.com>,
	b43-dev <b43-dev@lists.infradead.org>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: [RFC/RFT] b43: Load initial firmware file asynchronously
Date: Sat, 8 Dec 2012 22:41:57 +0100	[thread overview]
Message-ID: <20121208214157.GA21034@gauss> (raw)
In-Reply-To: <50C3AF0C.8000607@lwfinger.net>

On 12/08/12 at 03:20pm, Larry Finger wrote:
> On 12/08/2012 02:24 PM, Felix Janda wrote:
> >
> > Not much has changed. Say, if you want to have the complete dmesg output.
> 
> Yes, I messed that one up. Try this one - it is different in the error recovery.
> 
> Larry

Now I have a wlan0. Haven't tested it though yet. dmesg still prints some errors.

Felix
-------------- next part --------------
[    0.504374] b43-phy0: Broadcom 4306 WLAN found (core revision 5)
[    0.545047] b43-phy0: Found PHY: Analog 2, Type 2 (G), Revision 2
[    0.707107] async load of b43/ucode5.fw
[    0.740558] Broadcom 43xx driver loaded [ Features: PL ]
[   62.284907] In callback routine, firmware not available
[   62.284919] Pid: 632, comm: kworker/0:2 Not tainted 3.7.0-rc8 #22
[   62.284921] Call Trace:
[   62.284941]  [<c12eefaa>] b43_fw_cb+0x1a/0x30
[   62.284953]  [<c12b3c5b>] request_firmware_work_func+0x5b/0xb0
[   62.284960]  [<c104b540>] process_one_work+0x110/0x380
[   62.284966]  [<c12b3c00>] ? _request_firmware_prepare.isra.14+0x380/0x380
[   62.284970]  [<c104c2e9>] worker_thread+0x119/0x340
[   62.284974]  [<c104c1d0>] ? manage_workers+0x260/0x260
[   62.284982]  [<c1050abf>] kthread+0x8f/0xa0
[   62.284992]  [<c14dffb7>] ret_from_kernel_thread+0x1b/0x28
[   62.284996]  [<c1050a30>] ? __kthread_bind+0x30/0x30
[   62.299141] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   62.300427] Registered led device: b43-phy0::tx
[   62.300690] Registered led device: b43-phy0::rx
[   62.300950] Registered led device: b43-phy0::radio

  parent reply	other threads:[~2012-12-08 21:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06  3:47 [RFC/RFT] b43: Load initial firmware file asynchronously Larry Finger
2012-12-08 14:30 ` Felix Janda
2012-12-08 17:15   ` Larry Finger
2012-12-08 17:56     ` Felix Janda
2012-12-08 19:48       ` Larry Finger
     [not found]         ` <20121208202435.GA14973@gauss>
     [not found]           ` <50C3AF0C.8000607@lwfinger.net>
2012-12-08 21:41             ` Felix Janda [this message]
2012-12-08 22:19               ` Larry Finger
2012-12-08 22:35                 ` Felix Janda
2012-12-08 23:12                   ` Larry Finger
2012-12-09  7:44                     ` Felix Janda

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=20121208214157.GA21034@gauss \
    --to=felix.janda@posteo.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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).