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: Sun, 9 Dec 2012 08:44:50 +0100 [thread overview]
Message-ID: <20121209074450.GA1073@gauss> (raw)
In-Reply-To: <50C3C940.3060704@lwfinger.net>
On 12/08/12 at 05:12pm, Larry Finger wrote:
> > 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
Ok. (The behavior is now the same as if the firmware was built into the kernel.)
So thanks again for the fix.
Felix
WARNING: multiple messages have this Message-ID (diff)
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: Re: [RFC/RFT] b43: Load initial firmware file asynchronously
Date: Sun, 9 Dec 2012 08:44:50 +0100 [thread overview]
Message-ID: <20121209074450.GA1073@gauss> (raw)
In-Reply-To: <50C3C940.3060704@lwfinger.net>
On 12/08/12 at 05:12pm, Larry Finger wrote:
> > 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
Ok. (The behavior is now the same as if the firmware was built into the kernel.)
So thanks again for the fix.
Felix
next prev parent reply other threads:[~2012-12-09 7:44 UTC|newest]
Thread overview: 19+ 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 14:30 ` Felix Janda
2012-12-08 17:15 ` Larry Finger
2012-12-08 17:15 ` Larry Finger
2012-12-08 17:56 ` Felix Janda
2012-12-08 17:56 ` Felix Janda
2012-12-08 19:48 ` Larry Finger
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 21:41 ` Felix Janda
2012-12-08 22:19 ` Larry Finger
2012-12-08 22:19 ` Larry Finger
2012-12-08 22:35 ` Felix Janda
2012-12-08 22:35 ` Felix Janda
2012-12-08 23:12 ` Larry Finger
2012-12-08 23:12 ` Larry Finger
2012-12-09 7:44 ` Felix Janda [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=20121209074450.GA1073@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.