From: Larry Finger <Larry.Finger@lwfinger.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
Tom Gundersen <teg@jklm.no>, Andy Whitcroft <apw@canonical.com>,
Arend van Spriel <arend@broadcom.com>
Subject: Re: calling request_firmware() from module init will not work with recent/future udev versions
Date: Sat, 14 Jan 2012 12:20:15 -0600 [thread overview]
Message-ID: <4F11C75F.9030105@lwfinger.net> (raw)
In-Reply-To: <20120114175837.GA8504@tuxdriver.com>
On 01/14/2012 11:58 AM, John W. Linville wrote:
> Kay, thanks for the reports. Drivers should definitely be loading
> firmware at IFF_UP time.
As the maintainer for several drivers with this problem, I need to make some
changes. What call from mac80211 corresponds to IFF_UP?
I have looked into using asynchronous firmware loading, but I have not yet found
a good implementation.
Larry
next prev parent reply other threads:[~2012-01-14 18:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 15:25 calling request_firmware() from module init will not work with recent/future udev versions Kay Sievers
2012-01-14 17:58 ` John W. Linville
2012-01-14 18:20 ` Larry Finger [this message]
2012-01-14 19:59 ` Arend van Spriel
2012-01-14 19:59 ` Arend van Spriel
2012-01-14 20:13 ` Larry Finger
2012-01-14 20:13 ` Larry Finger
2012-01-14 20:15 ` Emmanuel Grumbach
2012-01-14 20:15 ` Emmanuel Grumbach
2012-01-14 18:45 ` Larry Finger
2012-01-14 19:26 ` Tom Gundersen
2012-01-15 10:02 ` Johannes Berg
2012-01-15 15:33 ` Kay Sievers
2012-01-15 15:33 ` Kay Sievers
2012-01-16 8:57 ` Johannes Berg
2012-01-16 12:05 ` Kay Sievers
2012-01-16 12:16 ` Johannes Berg
2012-07-19 10:46 ` Kay Sievers
2012-07-24 14:16 ` Johannes Berg
2012-07-24 14:32 ` Tom Gundersen
2012-07-24 17:50 ` Kay Sievers
2012-02-16 12:04 ` Arend van Spriel
2012-02-16 12:04 ` Arend van Spriel
2012-02-16 12:38 ` Johannes Berg
2012-02-16 13:09 ` Arend van Spriel
2012-02-16 13:09 ` Arend van Spriel
2012-02-16 14:39 ` Johannes Berg
2012-02-16 14:39 ` Johannes Berg
2012-02-20 17:43 ` Arend van Spriel
2012-02-20 17:43 ` Arend van Spriel
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=4F11C75F.9030105@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=apw@canonical.com \
--cc=arend@broadcom.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=teg@jklm.no \
/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.