Searched full:loading (Results 1 – 25 of 215) sorted by relevance
123456789
| /Documentation/leds/ |
| D | leds-lp55xx.rst | 93 echo 1 > /sys/class/firmware/lp5521/loading
95 echo 0 > /sys/class/firmware/lp5521/loading
103 echo 1 > /sys/class/firmware/lp55231/loading
105 echo 0 > /sys/class/firmware/lp55231/loading
115 echo 1 > /sys/class/firmware/lp5521/loading
117 echo 0 > /sys/class/firmware/lp5521/loading
126 echo 1 > /sys/class/firmware/lp5523/loading
128 echo 0 > /sys/class/firmware/lp5523/loading
132 As soon as 'loading' is set to 0, registered callback is called.
143 echo 1 > /sys/class/firmware/lp8501/loading
[all …]
|
| D | leds-lp5562.rst | 44 Before loading the LP5562 program data, engine_mux should be written between
45 the engine selection and loading the firmware.
47 RGB is used for loading RGB program data, W is used for W program data.
53 echo 1 > /sys/class/firmware/lp5562/loading
55 echo 0 > /sys/class/firmware/lp5562/loading
62 echo 1 > /sys/class/firmware/lp5562/loading
64 echo 0 > /sys/class/firmware/lp5562/loading
|
| /Documentation/translations/zh_CN/dev-tools/ |
| D | gdb-kernel-debugging.rst | 71 loading vmlinux
73 loading @0xffffffffa0020000: /home/user/linux/build/net/netfilter/xt_tcpudp.ko
74 loading @0xffffffffa0016000: /home/user/linux/build/net/netfilter/xt_pkttype.ko
75 loading @0xffffffffa0002000: /home/user/linux/build/net/netfilter/xt_limit.ko
76 loading @0xffffffffa00ca000: /home/user/linux/build/net/packet/af_packet.ko
77 loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko
79 loading @0xffffffffa0000000: /home/user/linux/build/drivers/ata/ata_generic.ko
94 loading @0xffffffffa0034000: /home/user/linux/build/lib/libcrc32c.ko
95 loading @0xffffffffa0050000: /home/user/linux/build/lib/lzo/lzo_compress.ko
96 loading @0xffffffffa006e000: /home/user/linux/build/lib/zlib_deflate/zlib_deflate.ko
[all …]
|
| /Documentation/translations/zh_TW/dev-tools/ |
| D | gdb-kernel-debugging.rst | 67 loading vmlinux
69 loading @0xffffffffa0020000: /home/user/linux/build/net/netfilter/xt_tcpudp.ko
70 loading @0xffffffffa0016000: /home/user/linux/build/net/netfilter/xt_pkttype.ko
71 loading @0xffffffffa0002000: /home/user/linux/build/net/netfilter/xt_limit.ko
72 loading @0xffffffffa00ca000: /home/user/linux/build/net/packet/af_packet.ko
73 loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko
75 loading @0xffffffffa0000000: /home/user/linux/build/drivers/ata/ata_generic.ko
90 loading @0xffffffffa0034000: /home/user/linux/build/lib/libcrc32c.ko
91 loading @0xffffffffa0050000: /home/user/linux/build/lib/lzo/lzo_compress.ko
92 loading @0xffffffffa006e000: /home/user/linux/build/lib/zlib_deflate/zlib_deflate.ko
[all …]
|
| /Documentation/dev-tools/ |
| D | gdb-kernel-debugging.rst | 59 Note: Some distros may restrict auto-loading of gdb scripts to known safe
60 directories. In case gdb reports to refuse loading vmlinux-gdb.py, add::
77 loading vmlinux
79 loading @0xffffffffa0020000: /home/user/linux/build/net/netfilter/xt_tcpudp.ko
80 loading @0xffffffffa0016000: /home/user/linux/build/net/netfilter/xt_pkttype.ko
81 loading @0xffffffffa0002000: /home/user/linux/build/net/netfilter/xt_limit.ko
82 loading @0xffffffffa00ca000: /home/user/linux/build/net/packet/af_packet.ko
83 loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko
85 loading @0xffffffffa0000000: /home/user/linux/build/drivers/ata/ata_generic.ko
101 loading @0xffffffffa0034000: /home/user/linux/build/lib/libcrc32c.ko
[all …]
|
| /Documentation/arch/x86/ |
| D | microcode.rst | 11 The kernel has a x86 microcode loading facility which is supposed to
12 provide microcode loading methods in the OS. Potential use cases are
16 The loader supports three loading methods:
21 The kernel can update microcode very early during boot. Loading
93 Late loading
103 The loading mechanism looks for microcode blobs in
107 Since kernel 5.19, late loading is not enabled by default.
111 Why is late loading dangerous?
188 Is the microcode suitable for late loading?
191 Late loading is done when the system is fully operational and running
[all …]
|
| D | usb-legacy-support.rst | 35 can be solved by loading the USB drivers prior to loading the
|
| /Documentation/firmware_class/ |
| D | hotplug-script | 11 echo 1 > /sys/$DEVPATH/loading
13 echo 0 > /sys/$DEVPATH/loading
15 echo -1 > /sys/$DEVPATH/loading
|
| /Documentation/driver-api/firmware/ |
| D | fallback-mechanisms.rst | 58 interface as a loading facility:
63 First lets document the shared sysfs loading facility.
65 Firmware sysfs loading facility
77 given that originally the only firmware loading mechanism available was the
83 To load firmware using the sysfs interface we expose a loading indicator,
86 * /sys/$DEVPATH/loading
89 To upload firmware you will echo 1 onto the loading file to indicate
90 you are loading firmware. You then write the firmware into the data file,
92 the loading file.
95 direct firmware loading fails and if the fallback mechanism is enabled for your
[all …]
|
| D | fw_upload.rst | 11 upload uses the same *loading* and *data* sysfs files described in the
21 firmware upload by echoing a 1 to the *loading* sysfs file for the target
23 file. After writing the firmware data, the user echos 0 to the *loading*
24 sysfs file to signal completion. Echoing 0 to *loading* also triggers the
116 In addition to the *loading* and *data* sysfs files, there are additional
|
| D | lookup-order.rst | 19 is issued or the custom firmware loading is relied upon for firmware
20 loading up to the timeout value.
|
| /Documentation/admin-guide/acpi/ |
| D | ssdt-overlays.rst | 18 way to augment firmware ACPI configuration is by dynamically loading
70 Loading ACPI SSDTs from initrd
73 This option allows loading of user defined SSDTs from initrd and it is useful
79 in loading multiple tables. Only SSDT and OEM tables are allowed. See
98 Loading ACPI SSDTs from EFI variables
103 is also work underway to implement EFI support for loading user defined SSDTs
104 and using this method will make it easier to convert to the EFI loading
168 Loading ACPI SSDTs from configfs
171 This option allows loading of user defined SSDTs from user space via the configfs
176 New tables can be loading by creating new directories in /sys/kernel/config/acpi/table
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-firmware | 7 after you echo 1 to the loading sysfs file. When the firmware
8 image write is complete, echo 0 to the loading sysfs file. This
37 What: /sys/class/firmware/.../loading
41 Description: The loading sysfs file is used for both firmware-fallback and
42 for firmware uploads. Echo 1 onto the loading file to indicate
|
| D | evm | 81 Loading an HMAC key is the only way to disable metadata
84 Until key loading has been signaled EVM can not create
86 INTEGRITY_UNKNOWN. Loading keys and signaling EVM
90 creating and loading existing trusted/encrypted keys,
94 core/ima-setup) have support for loading keys at boot
|
| /Documentation/core-api/ |
| D | symbol-namespaces.rst | 16 === 4 Loading Modules that use namespaced Symbols
29 its configuration, reject loading the module or warn about a missing import.
132 4. Loading Modules that use namespaced Symbols
135 At module loading time (e.g. ``insmod``), the kernel will check each symbol
138 the kernel is to reject loading modules that don't specify sufficient imports.
139 An error will be logged and loading will be failed with EINVAL. In order to
140 allow loading of modules that don't satisfy this precondition, a configuration
142 enable loading regardless, but will emit a warning.
|
| /Documentation/admin-guide/ |
| D | dell_rbu.rst | 48 /sys/class/firmware/dell_rbu/loading
94 1) echo 1 > /sys/class/firmware/dell_rbu/loading
96 3) echo 0 > /sys/class/firmware/dell_rbu/loading
103 echo -1 > /sys/class/firmware/dell_rbu/loading
|
| D | init.rst | 30 hardware. In case you tried loading a non-binary file here (shell script?),
39 (after all loading the init binary is a CRITICAL and hard transition step
|
| /Documentation/bpf/ |
| D | bpf_licensing.rst | 72 Loading BPF program into the Linux kernel is similar to loading a kernel
74 kernel. BPF program loading follows the same license checking rules as kernel
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | wkup_m3_rproc.txt | 7 binary to accomplish this. The wkup_m3 remoteproc driver handles the loading of
28 - ti,pm-firmware: Name of firmware file to be used for loading and
|
| /Documentation/userspace-api/ebpf/ |
| D | index.rst | 8 source code or loading kernel modules. eBPF programs can be attached to various
|
| /Documentation/networking/device_drivers/ethernet/netronome/ |
| D | nfp.rst | 48 Recent versions of management firmware supports loading application
49 firmware from flash when the host driver gets probed. The firmware loading
92 is system loading wrong driver or firmware on boot, but when driver is
106 nfp: netronome/nic_AMDA0081-0001_1x40.nffw: found, loading...
125 Firmware loading policy
128 Firmware loading policy is controlled via three HWinfo parameters
|
| /Documentation/devicetree/bindings/fpga/ |
| D | lattice-machxo2-spi.txt | 3 Lattice MachXO2 FPGAs support a method of loading the bitstream over
|
| /Documentation/admin-guide/media/ |
| D | opera-firmware.rst | 32 (if you have enabled firmware loading
|
| /Documentation/iio/ |
| D | iio_configfs.rst | 76 Each trigger type has its own directory under /config/iio/triggers. Loading
87 Loading iio-trig-hrtimer module will register hrtimer trigger types allowing
|
| /Documentation/hwmon/ |
| D | pm6764tr.rst | 30 maintaining the best efficiency over all loading conditions without compromising transient
|
123456789