Lines Matching refs:in
9 Today, the most extended way to use firmware in the Linux kernel is linking
10 it statically in a header file. Which has political and technical issues:
24 in the below search path of root filesystem:
34 if firmware_class is built in kernel(the general situation)
38 - hotplug gets called with a firmware identifier in $FIRMWARE
48 5), kernel: grows a buffer in PAGE_SIZE increments to hold the image as it
49 comes in.
55 image in fw_entry->{data,size}. If something went wrong
72 # Both $DEVPATH and $FIRMWARE are already provided in the environment.
87 for testing and completeness, they are not called in normal use.
89 - There is also /sys/class/firmware/timeout which holds a timeout in
92 - request_firmware_nowait() is also provided for convenience in
94 in atomic contexts.
97 about in-kernel persistence:
100 firmware images in non-swappable kernel memory or even in the kernel image
105 - Why OPTIONAL in-kernel persistence may be a good idea sometimes:
112 - The filesystem is stored in a disk behind an scsi device