Searched full:onto (Results 1 – 25 of 138) sorted by relevance
123456
| /Documentation/ABI/testing/ |
| D | sysfs-class-firmware | 42 for firmware uploads. Echo 1 onto the loading file to indicate
44 -1 onto this file to abort the data write or echo 0 onto this
|
| D | sysfs-platform-dell-privacy-wmi | 19 shutter assembly that is built onto the camera module to block capturing images
54 shutter assembly that is built onto the camera module to block capturing images
|
| D | sysfs-firmware-gsmi | 29 This file takes a binary blob and passes it onto
|
| /Documentation/admin-guide/blockdev/ |
| D | ramdisk.rst | 36 allowing one to squeeze more programs onto an average installation or
117 e) Put the kernel onto the floppy::
121 f) Put the RAM disk image onto the floppy, after the kernel. Use an offset
123 (possibly larger) kernel onto the same floppy later without overlapping
|
| /Documentation/userspace-api/media/v4l/ |
| D | depth-formats.rst | 9 Depth data provides distance to points, mapped onto the image plane
|
| /Documentation/devicetree/bindings/display/ |
| D | st,stm32mp25-lvds.yaml | 16 onto the LVDS PHY.
20 pixels onto the data lanes of the PHY
|
| /Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 104 timer back onto one of the CPUs in question.
111 1. Force networking interrupts onto other CPUs.
123 1. Force block-device interrupts onto some other CPU.
135 1. Force block-device interrupts onto some other CPU.
150 3. Force interrupts for drivers using tasklets onto other CPUs,
189 back onto one of the CPUs in question.
|
| /Documentation/devicetree/bindings/bus/ |
| D | omap-ocp2scp.txt | 8 - ranges : the child address space are mapped 1:1 onto the parent address space
|
| /Documentation/driver-api/firmware/ |
| D | introduction.rst | 9 * Device driver firmware, required to be loaded onto device
|
| D | fallback-mechanisms.rst | 89 To upload firmware you will echo 1 onto the loading file to indicate
91 and you notify the kernel the firmware is ready by echo'ing 0 onto
193 onto the sysfs interface by the timeout value an error is sent to the
|
| /Documentation/arch/arm/sa1100/ |
| D | cerf.rst | 25 In order to get this kernel onto your Cerf, you need a server that runs
|
| /Documentation/admin-guide/device-mapper/ |
| D | delay.rst | 52 # onto the same backing device at offset 0 sectors.
|
| D | linear.rst | 6 device onto a linear range of another device. This is the basic building
|
| /Documentation/driver-api/media/drivers/ |
| D | sh_mobile_ceu_camera.rst | 47 mapped back onto the client's source plane.
77 current sensor scales onto input window - this is user S_CROP:
|
| D | contributors.rst | 32 - for CyberLogin for Linux which allows logging onto EON
|
| /Documentation/networking/devlink/ |
| D | i40e.rst | 58 - Unique identifier of the firmware image file that was loaded onto
|
| D | devlink-info.rst | 114 - Identifier of a distribution package which was flashed onto the device.
217 may need to load onto devices via the ``MODULE_FIRMWARE()`` macro. These,
|
| /Documentation/devicetree/bindings/dma/ |
| D | sifive,fu540-c000-pdma.yaml | 38 "sifive,fu540-c000-pdma" for the SiFive PDMA v0 as integrated onto the
|
| /Documentation/devicetree/bindings/media/ |
| D | imx.txt | 33 controller's 32-bit output image bus onto four 16-bit parallel busses
|
| /Documentation/devicetree/bindings/pwm/ |
| D | pwm-sifive.yaml | 36 "sifive,fu740-c000-pwm" for the SiFive PWM v0 as integrated onto the
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-sifive.yaml | 29 as integrated onto the SiFive FU540 and FU740 chip resp, and "sifive,spi0"
|
| /Documentation/userspace-api/ |
| D | sysfs-platform_profile.rst | 35 representation onto this fixed set.
|
| /Documentation/networking/ |
| D | scaling.rst | 313 to enqueue packets onto the backlog of another CPU and to wake up that
337 counter. The CPU index represents the *current* CPU onto which packets
349 been enqueued onto the currently designated CPU for flow i (of course,
358 table), the packet is enqueued onto that CPU’s backlog. If they differ,
543 system, XPS is preferably configured so that each CPU maps onto one queue.
545 queue can also map onto one CPU, resulting in exclusive pairings that
|
| /Documentation/devicetree/bindings/usb/ |
| D | omap-usb.txt | 57 - ranges: the child address space are mapped 1:1 onto the parent address space
|
| /Documentation/devicetree/bindings/iio/ |
| D | mount-matrix.txt | 57 as the gravity vector is projected 1:1 onto the sensors (z)-axis.
60 is projected onto the (x,y) plane of the display panel.
|
123456