| 1 |
===================== |
| 2 |
Firmware search paths |
| 3 |
===================== |
| 4 |
|
| 5 |
The following search paths are used to look for firmware on your |
| 6 |
root filesystem. |
| 7 |
|
| 8 |
* fw_path_para - module parameter - default is empty so this is ignored |
| 9 |
* /lib/firmware/updates/UTS_RELEASE/ |
| 10 |
* /lib/firmware/updates/ |
| 11 |
* /lib/firmware/UTS_RELEASE/ |
| 12 |
* /lib/firmware/ |
| 13 |
|
| 14 |
The module parameter ''path'' can be passed to the firmware_class module |
| 15 |
to activate the first optional custom fw_path_para. The custom path can |
| 16 |
only be up to 256 characters long. The kernel parameter passed would be: |
| 17 |
|
| 18 |
* 'firmware_class.path=$CUSTOMIZED_PATH' |
| 19 |
|
| 20 |
There is an alternative to customize the path at run time after bootup, you |
| 21 |
can use the file: |
| 22 |
|
| 23 |
* /sys/module/firmware_class/parameters/path |
| 24 |
|
| 25 |
You would echo into it your custom path and firmware requested will be searched |
| 26 |
for there first. Be aware that newline characters will be taken into account |
| 27 |
and may not produce the intended effects. For instance you might want to use: |
| 28 |
|
| 29 |
echo -n /path/to/script > /sys/module/firmware_class/parameters/path |
| 30 |
|
| 31 |
to ensure that your script is being used. |