From: Larry Finger <Larry.Finger@lwfinger.net>
To: Felix Janda <felix.janda@posteo.de>
Cc: John W Linville <linville@tuxdriver.com>,
b43-dev <b43-dev@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC/RFT] b43: Load initial firmware file asynchronously
Date: Sat, 08 Dec 2012 17:12:00 -0600 [thread overview]
Message-ID: <50C3C940.3060704@lwfinger.net> (raw)
In-Reply-To: <20121208223509.GA21258@gauss>
On 12/08/2012 04:35 PM, Felix Janda wrote:
> On 12/08/12 at 04:19pm, Larry Finger wrote:
>>> Now I have a wlan0. Haven't tested it though yet. dmesg still prints some errors.
>>
>> That is not an error - I just left a diagnostic in the code. Please let me know
>> if it works. It should as we only touched the firmware loading.
>>
>> Is it OK if I use a "Reported-and-Tested by: <you>?
>>
>> Larry
>
> It's OK. Over christmas I'll do some thoroughful testing.
>
> The delay of 60 seconds will stay?
As this happens while user-space is getting started, there is little we can do.
On my dual-core x86_64 system with each CPU running at 2 GHz, it takes 24 sec
before the fw is loaded. At least other things happen in parallel.
Larry
next prev parent reply other threads:[~2012-12-08 23:12 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
2012-12-08 22:19 ` Larry Finger
2012-12-08 22:35 ` Felix Janda
2012-12-08 23:12 ` Larry Finger [this message]
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=50C3C940.3060704@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=felix.janda@posteo.de \
--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).