Documentation: firmware: Clarify firmware path usage
Newline characters will be taken into account for the firmware search path parameter, warn users about that and provide an example using 'echo -n' such that it clarifies the typical use of that parameter. Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> Link: https://lore.kernel.org/r/20230402135423.3235-1-f.fainelli@gmail.com Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
parent
7332f9e45d
commit
b645fc696b
|
@ -22,5 +22,10 @@ can use the file:
|
||||||
|
|
||||||
* /sys/module/firmware_class/parameters/path
|
* /sys/module/firmware_class/parameters/path
|
||||||
|
|
||||||
You would echo into it your custom path and firmware requested will be
|
You would echo into it your custom path and firmware requested will be searched
|
||||||
searched for there first.
|
for there first. Be aware that newline characters will be taken into account
|
||||||
|
and may not produce the intended effects. For instance you might want to use:
|
||||||
|
|
||||||
|
echo -n /path/to/script > /sys/module/firmware_class/parameters/path
|
||||||
|
|
||||||
|
to ensure that your script is being used.
|
||||||
|
|
Loading…
Reference in New Issue