From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Tom Gundersen <teg@jklm.no>, Andy Whitcroft <apw@canonical.com>
Subject: Re: calling request_firmware() from module init will not work with recent/future udev versions
Date: Thu, 16 Feb 2012 15:39:05 +0100 [thread overview]
Message-ID: <1329403145.3915.10.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4F3D0012.9070808@broadcom.com>
On Thu, 2012-02-16 at 14:09 +0100, Arend van Spriel wrote:
> > When the firmware loading fails, the driver should unbind from the
> > device that it failed for, and the retrying behaviour doesn't change
> > (and requires a rebind)
> That helps. My driver was happily bound to the device until unloading
> the driver or unplugging the device.
Right, if it fails you should call device_release_driver()
johannes
next prev parent reply other threads:[~2012-02-16 14:39 UTC|newest]
Thread overview: 22+ 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
2012-01-14 19:59 ` Arend van Spriel
2012-01-14 20:13 ` Larry Finger
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-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:38 ` Johannes Berg
2012-02-16 13:09 ` Arend van Spriel
2012-02-16 14:39 ` Johannes Berg [this message]
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=1329403145.3915.10.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=apw@canonical.com \
--cc=arend@broadcom.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-wireless@vger.kernel.org \
--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 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).