firmware: revamp firmware documentation
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>
This commit is contained in:

committed by
Greg Kroah-Hartman

parent
880444e214
commit
113ccc3837
26
Documentation/driver-api/firmware/fw_search_path.rst
Normal file
26
Documentation/driver-api/firmware/fw_search_path.rst
Normal file
@@ -0,0 +1,26 @@
|
||||
=====================
|
||||
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.
|
Reference in New Issue
Block a user