linux-kernel - Question about loading firmware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Sun, 12 Feb 2012 13:08:28 -0600
From:	Larry Finger <Larry.Finger@...inger.net>
To:	LKML <linux-kernel@...r.kernel.org>,
	driverdevel <devel@...verdev.osuosl.org>,
	wireless <linux-wireless@...r.kernel.org>
Subject: Question about loading firmware

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/