Lines Matching full: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
21  kernel(driver): calls request_firmware(&fw_entry, $FIRMWARE, device)
24  	- /sys/class/firmware/xxx/{loading,data} appear.
25 	- hotplug gets called with a firmware identifier in $FIRMWARE
27 		- hotplug: echo 1 > /sys/class/firmware/xxx/loading
33 					/sys/class/firmware/xxx/data
39 		- hotplug: echo 0 > /sys/class/firmware/xxx/loading
41  kernel: request_firmware() returns and the driver has the firmware
47 		 the firmware image and any related resource.
52 	 if(request_firmware(&fw_entry, $FIRMWARE, device) == 0)
59 	# Both $DEVPATH and $FIRMWARE are already provided in the environment.
61 	HOTPLUG_FW_DIR=/usr/lib/hotplug/firmware/
64 	cat $HOTPLUG_FW_DIR/$FIRMWARE > /sysfs/$DEVPATH/data
70  - "echo -1 > /sys/class/firmware/xxx/loading" will cancel the load at
76  - There is also /sys/class/firmware/timeout which holds a timeout in
80    user contexts to request firmware asynchronously, but can't be called
87  firmware images in non-swappable kernel memory or even in the kernel image
94 	- If the device that needs the firmware is needed to access the
96 	  firmware reloaded, it won't be possible to get it from userspace.
98 		- A diskless client with a network card that needs firmware.
100 		  that needs firmware.
106    on the setup, so I think that the choice on what firmware to make