mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-12-04 17:44:14 +08:00
113ccc3837
Understanding this code is getting out of control without any notes. Give the firmware_class driver a much needed documentation love, and while at it convert it to the new sphinx documentation format. v2: typos and small fixes Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
27 lines
830 B
ReStructuredText
27 lines
830 B
ReStructuredText
=====================
|
|
Firmware search paths
|
|
=====================
|
|
|
|
The following search paths are used to look for firmware on your
|
|
root filesystem.
|
|
|
|
* fw_path_para - module parameter - default is empty so this is ignored
|
|
* /lib/firmware/updates/UTS_RELEASE/
|
|
* /lib/firmware/updates/
|
|
* /lib/firmware/UTS_RELEASE/
|
|
* /lib/firmware/
|
|
|
|
The module parameter ''path'' can be passed to the firmware_class module
|
|
to activate the first optional custom fw_path_para. The custom path can
|
|
only be up to 256 characters long. The kernel parameter passed would be:
|
|
|
|
* 'firmware_class.path=$CUSTOMIZED_PATH'
|
|
|
|
There is an alternative to customize the path at run time after bootup, you
|
|
can use the file:
|
|
|
|
* /sys/module/firmware_class/parameters/path
|
|
|
|
You would echo into it your custom path and firmware requested will be
|
|
searched for there first.
|