Searched full:effectively (Results 1 – 25 of 458) sorted by relevance
12345678910>>...19
40 Subsampling the chroma component effectively creates chroma values that can be46 value of two consecutive pixels. It effectively models the chroma of a pixel
69 Another note that each connection occupies 128 bytes effectively and298 needs to be large enough to effectively fit all the destinations316 enough to effectively fit all the destinations multiplied by their
1 # The async firmware timeout is set to 1 second (but ends up being effectively
19 * This effectively disable read()/write() on /dev/mem.
36 * This is effectively shorthand for "memchr_inv(from, 0, size) == NULL" for
13 the 'ip' utility in order to effectively use VLANs.
41 * All 32bit addresses are effectively valid for vmalloc...
16 The bitrate is very slow (effectively no more than 36 bytes per second)
23 be used rather effectively as scratch registers by the kernel.
59 * All 32bit addresses are effectively valid for vmalloc...
16 retransmissions effectively through fast retransmit instead of
52 * down and up as needed. Start=0 and length=2G effectively iterates over
52 * UPROBE_HANDLER_REMOVE is effectively ignored.103 * uprobe effectively went away (the last consumer unsubscribed). In this
33 floor. This offset is effectively canceled at every conversion,
32 * effectively 2nd timeout is ignored within hardware.34 * First timeout is effectively watchdog pretimeout.
71 that translates I2C commands to CFAM or SCOM operations, effectively
16 firmware and thus effectively many different revisions of the uGuru.
90 The LM64 is effectively an LM63 with GPIO lines. The driver does not
19 waiting for the workload to complete. Effectively this terminates the workload
34 * Pin the page (effectively FOLL_PIN, which is an mm/ internal flag).
20 * This workaround effectively recovers the header bits. in img_ir_rc6_scancode()
10 Unfortunately, to effectively test the support for the system-wide suspend and
42 buffers. The triggers are effectively a 'capture
51 * methods call sync_dirty_buffer() and thus effectively write one block in sync_filesystem()90 * which effectively also waits for all flusher threads to finish doing
46 stubs' exception vector value. This effectively disables an existing