Searched full:nearly (Results 1 – 25 of 164) sorted by relevance
1234567
23 setting is very flexible - able to set nearly arbitrary modes from any timing.27 * Ability to add a nearly arbitrary number of displays to any USB 2.034 * The actual hardware functionality of DisplayLink chips matches nearly
53 /* Check if ring is nearly full */ in qat_alg_try_enqueue()
48 u32 statne_h; /* 0x418 - queue nearly empty */
18 merges would be nearly impossible. Some problems encountered by98 development cycle included 1,126 merge commits - nearly 9% of the total.
62 The provider API is admittedly not nearly as straightforward as the one for
118 are nearly indistinguishable from on-chip integrated RAM.
104 value since they are the same in nearly all cases.
551 * for nearly all cases. */ in ipic_mask_irq()570 * for nearly all cases. */ in ipic_ack_irq()593 * for nearly all cases. */ in ipic_mask_irq_and_ack()
11 digitized images in memory. Today nearly all devices can capture at full
68 in nearly constant time. Instead of scanning the whole MTD device it
61 * because nearly all memset invocations in the kernel clear memory and
172 * iounmap unmaps nearly everything, so be careful
145 * to avoid livelocks if the log grant space is nearly exhausted due to the
47 * differently than multi-tile platforms like PVC where nearly everything is
129 This currently performs nearly no instrumentation due to the
26 nearly NE2000 compatible but need a separate driver due to a few
134 /* Nearly all registers have status bits mixed in, except a few */ in is_volatile_reg()
50 biggest system interfaces in fact include nearly all of the rest SoC
2552 loff_t nearly = round_up(offset, PAGE_SIZE); in ceph_zero_pagecache_range() local2553 if (offset < nearly) { in ceph_zero_pagecache_range()2554 loff_t size = nearly - offset; in ceph_zero_pagecache_range()2621 u64 nearly, t; in ceph_zero_objects() local2624 nearly = offset + object_set_size - 1; in ceph_zero_objects()2625 t = nearly; in ceph_zero_objects()2626 nearly -= do_div(t, object_set_size); in ceph_zero_objects()2628 while (length && offset < nearly) { in ceph_zero_objects()
30 changers. But it allows to handle nearly all possible cases. It knows
15 nearly 2000.
84 * All of tasks can read from the buffer nearly simultaneously, but the in hwdep_read_resp_buf()
74 entry. This consumes nearly 2MB of RAM once the kernel
134 - SCHED_BATCH: Does not preempt nearly as often as regular tasks
55 * __free_io_area unmaps nearly everything, so be careful