From: Larry Finger <Larry.Finger@lwfinger.net>
To: LKML <linux-kernel@vger.kernel.org>,
driverdevel <devel@driverdev.osuosl.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: Question about loading firmware
Date: Sun, 12 Feb 2012 13:08:28 -0600 [thread overview]
Message-ID: <4F380E2C.3050303@lwfinger.net> (raw)
Drivers b43 and b43legacy both load their firmware from their probe routines,
which is a problem with the latest udev implementations, and I'm trying to fix
that problem.
The complication is that they need to load several (3 or 4) firmware files. When
I tried to use request_firmware_nowait() to load them in parallel, I got
warnings that I was trying to create a duplicate name in sysfs. I presume this
is because each of the tasks has the same name - I used the default THIS_MODULE
value for the first argument. I'm not sure that I could change that - I don't
see any examples in the existing source.
If I changed the probe routine to start a workqueue item that called the
firmware loading routines, could I safely use request_firmware() in that case?
If so, it would be a clean solution.
Thanks,
Larry
reply other threads:[~2012-02-12 19:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F380E2C.3050303@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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
Powered by JetHome