linux-kernel - Re: request_firmware() and in-kernel modules

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071021040757.GC24869@kroah.com>
Date:	Sat, 20 Oct 2007 21:07:57 -0700
From:	Greg KH <greg@...ah.com>
To:	Timur Tabi <timur@...escale.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: request_firmware() and in-kernel modules

On Fri, Oct 19, 2007 at 12:35:38PM -0500, Timur Tabi wrote:
> If my driver is compiled in-kernel (and I have module support turned off), 
> can I still use request_firmware()?

Yes.

> If my driver is loaded before the file system drivers are loaded, how
> can a user process copy the firmware to the
> /sys/class/firwmare/.../data device?

I'd recommend using the non-blocking mode, that way, when userspace
finally gets running, it can handle the firmware events properly, and
your kernel code will have not timed out already.

thanks,

greg k-h
-
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/