Searched full:another (Results 1 – 25 of 638) sorted by relevance
12345678910>>...26
/Documentation/userspace-api/media/v4l/ |
D | dev-mem2mem.rst | 10 otherwise convert video data from one format into another format, in memory. 27 the hardware and reprogram it whenever another file handler gets access. 30 file handle is visible through another file handle).
|
D | app-pri.rst | 13 channel. Another objective is to permit low priority applications 30 after another application obtained higher priority.
|
D | vidioc-g-priority.rst | 73 requests another. 91 Another application already requested higher priority.
|
D | pixfmt-v4l2.rst | 116 conversion, it will return another supported colorspace. 160 conversion, it will return another supported encoding. 174 conversion, it will return another supported encoding. 190 conversion, it will return another supported quantization. 203 conversion, it will return another supported transfer function.
|
/Documentation/ABI/testing/ |
D | sysfs-bus-i2c-devices-pca954x | 13 with an address that conflicts with another 14 device on another mux on the same parent bus.
|
/Documentation/admin-guide/namespaces/ |
D | compatibility-list.rst | 31 other object in another namespace. 36 access permissions to files, belonging to user 10 in another
|
/Documentation/devicetree/bindings/watchdog/ |
D | aspeed-wdt.txt | 20 This is useful in situations where another watchdog engine on chip is 34 - none: No reset is performed on timeout. Assumes another watchdog
|
/Documentation/networking/ |
D | x25.rst | 27 implementation is being done as part of another protocol project (SNA) and 30 Just when you thought that it could not become more confusing, another
|
/Documentation/devicetree/bindings/ |
D | example-schema.yaml | 41 # isn't another way to express a constraint of the last string value. 168 description: Child nodes are just another property from a json-schema 196 # another property. A typical case is a specific 'compatible' value changes the 226 # This can't be used in cases where another schema is referenced 228 # If and only if another schema is referenced and arbitrary children nodes can
|
/Documentation/devicetree/bindings/rng/ |
D | microchip,pic32-rng.txt | 4 another true random number generator.
|
/Documentation/i2c/ |
D | slave-interface.rst | 11 driver. While another I2C master on the bus can access it like a regular 77 Another I2C master wants to write data to us. This event should be sent once 88 Another I2C master wants to read data from us. This event should be sent once 98 Another I2C master has sent a byte to us which needs to be set in 'val'. If 'ret' 108 The bus driver requests the next byte to be sent to another I2C master in
|
/Documentation/filesystems/ext4/ |
D | mmp.rst | 15 filesystem is active on another machine and the open fails. If the MMP 22 MMP sequence number, then another node (node B) has mounted the
|
/Documentation/admin-guide/cgroup-v1/ |
D | freezer-subsystem.rst | 16 quiescent state. Once the tasks are quiescent another task can 21 to another node and restarting the tasks there. 47 Another example of a program which catches and responds to these
|
/Documentation/RCU/ |
D | rculist_nulls.rst | 76 "If the object is moved from one list to another list in-between the 90 from a chain, and inserted into another chain. If new chain was empty 141 to another chain) checking the final 'nulls' value if 170 * We probably met an item that was moved to another chain.
|
/Documentation/security/ |
D | credentials.rst | 13 object acts upon another: 52 A subject is an object that is acting upon another object. 209 an object with another label. 279 task to alter another's credentials. This means the ``capset()`` system call 357 Accessing Another Task's Credentials 361 same is not true of a task wanting to access another task's credentials. It 383 Should it be necessary to hold another task's credentials for a long period of 396 There are a couple of convenience functions to access bits of another task's 413 Should some other single aspect of another task's credentials need to be 431 alter those of another task. This means that it doesn't need to use any
|
/Documentation/devicetree/bindings/firmware/ |
D | cznic,turris-mox-rwtm.txt | 7 This device tree node should be used on Turris Mox, or potentially another A3700
|
/Documentation/devicetree/bindings/memory-controllers/ |
D | mvebu-sdram-controller.txt | 4 differs from one SoC variant to another, but they also share a number
|
/Documentation/admin-guide/ |
D | numastat.rst | 28 numa_miss A process wanted to allocate memory from another node, 32 but ended up with memory from another node.
|
/Documentation/ABI/removed/ |
D | sysfs-kernel-uids | 10 shares, then they will get equal CPU bandwidth. Another
|
/Documentation/admin-guide/device-mapper/ |
D | persistent-data.rst | 14 - Another btree-based caching target posted to dm-devel 15 - Another multi-snapshot target based on a design of Daniel Phillips
|
/Documentation/devicetree/bindings/i2c/ |
D | i2c.txt | 71 states that there is another master active on this bus. The OS can use 107 Another flag is I2C_OWN_SLAVE_ADDRESS to mark addresses on which we 128 It can contain any map needing another address than default one.
|
D | i2c-arb-gpio-challenge.txt | 14 problems (hard to tell if i2c issues were caused by one master, another, or 51 - wait-retry-us: we'll attempt another claim after this many microseconds.
|
/Documentation/devicetree/bindings/gpio/ |
D | ibm,ppc4xx-gpio.txt | 5 another purpose. GPIO outputs are separately programmable to emulate
|
/Documentation/maintainer/ |
D | rebasing-and-merging.rst | 62 have pulled changes from another developer's repository, you are now a 187 Another reason for doing merges of upstream or another subsystem tree is to 189 sometimes a cross-merge with another tree is the best way to resolve them; 195 needed. Merging another subsystem tree to resolve a dependency risks
|
/Documentation/virt/kvm/ |
D | running-nested-guests.rst | 5 A nested guest is the ability to run a guest inside another guest (it 41 hypervisor running on bare metal, adding another layer and 185 Migrating an L1 guest, with a *live* nested guest in it, to another 203 - Migrating a nested guest (L2) to another L1 guest on the *same* bare 206 - Migrating a nested guest (L2) to another L1 guest on a *different*
|
12345678910>>...26