Lines Matching refs:firmware

9  Today, the most extended way to use firmware in the Linux kernel is linking
12   1) Some firmware is not legal to redistribute.
13   2) The firmware occupies memory permanently, even though it often is just
15   3) Some people, like the Debian crowd, don't consider some firmware free
26 		"/lib/firmware/updates/" UTS_RELEASE,
27 		"/lib/firmware/updates",
28 		"/lib/firmware/" UTS_RELEASE,
29 		"/lib/firmware"
37  	- /sys/class/firmware/xxx/{loading,data} appear.
38 	- hotplug gets called with a firmware identifier in $FIRMWARE
40 		- hotplug: echo 1 > /sys/class/firmware/xxx/loading
46 					/sys/class/firmware/xxx/data
52 		- hotplug: echo 0 > /sys/class/firmware/xxx/loading
54  7), kernel: request_firmware() returns and the driver has the firmware
60 		 the firmware image and any related resource.
74 	HOTPLUG_FW_DIR=/usr/lib/hotplug/firmware/
83  - "echo -1 > /sys/class/firmware/xxx/loading" will cancel the load at
89  - There is also /sys/class/firmware/timeout which holds a timeout in
93    user contexts to request firmware asynchronously, but can't be called
100  firmware images in non-swappable kernel memory or even in the kernel image
107 	- If the device that needs the firmware is needed to access the
109 	  firmware reloaded, it won't be possible to get it from userspace.
111 		- A diskless client with a network card that needs firmware.
113 		  that needs firmware.
119    on the setup, so I think that the choice on what firmware to make
122  about firmware cache:
124  After firmware cache mechanism is introduced during system sleep,
126  resume callback, and callers needn't cache the firmware by
127  themselves any more for dealing with firmware loss during system