Searched full:few (Results 1 – 25 of 1642) sorted by relevance
12345678910>>...66
41 br.ctop.dptk.few 0b45 br.ret.sptk.few rp82 br.ctop.dptk.few 0b86 br.ret.sptk.few rp126 br.ctop.dptk.few 0b130 br.ret.sptk.few rp175 br.ctop.dptk.few 0b179 br.ret.sptk.few rp
84 (p7) br.cond.spnt.few .memcpy_short85 (p6) br.cond.spnt.few .memcpy_long105 br.ctop.dptk.few 1b149 br.ctop.dptk.few 1b162 * by storing the last few bytes using sub-word copying. If the source256 br.sptk.few b6261 // less than 8) and t0 contains the last few bytes of the src buffer:286 br.ctop.dptk.few 1b; \
85 (p_scr) br.cond.dptk.many .move_bytes_unaligned // go move just a few (M_B_U)121 (p_scr) br.cond.dpnt.many .fraction_of_line // go move just a few152 br.cloop.dptk.few .pref_l1a191 br.cloop.dptk.few .l1ax194 cmp.le p_scr, p0 = 8, cnt // just a few bytes left ?222 br.cloop.dptk.few .pref_l1b245 br.cloop.dptk.few .l1bx248 cmp.gt p_scr, p0 = 8, cnt // just a few bytes left ?278 cmp.gt p_scr, p0 = 8, cnt // just a few bytes left ?301 (p_scr) br.cond.dpnt.few .restore_and_exit
136 br.cloop.dptk.few .prefetch153 (p10) br.dpnt.few .aligned_src_tail166 br.ctop.dptk.few 1b315 br.cloop.dptk.few 1b326 (p8) br.dpnt.few .noloop349 br.cond.sptk.few b6513 br.ctop.dptk.few 1b;; \516 br.sptk.few .unaligned_src_tail /* branch out of jump table */ \646 (p8) br.call.sptk.few b0=__copy_user // recursive call
49 br.cloop.sptk.few .fetch74 br.cloop.sptk.few 1b
80 (p7) br.cond.dpnt.few 4f86 br.cloop.sptk.few 3b91 br.sptk.few 2b131 br.sptk.few .dest_page138 (p6) br.cond.sptk.few .loop;;142 (p6) br.cond.sptk.few .loop;;145 (p6) br.cond.sptk.few .end_loop;;148 (p6) br.cond.sptk.few .loop160 br.ctop.sptk.few 1b161 br.sptk.few .loop
14 The SoC has a few registers (DEVCPU_GCB:CHIP_REGS) handling miscellaneous31 The SoC has a few registers (ICPU_CFG:CPU_SYSTEM_CTRL) handling configuration of47 The SoC has a few registers (HSIO) handling miscellaneous functionalities:
141 "br.few 3f\n" in arch_read_lock_flags()149 "(p7) br.cond.spnt.few 2b\n" in arch_read_lock_flags()155 "(p7) br.cond.spnt.few 1b\n" in arch_read_lock_flags()195 "br.few 3f;;\n" in arch_write_lock_flags()202 "(p7) br.cond.spnt.few 2b\n" in arch_write_lock_flags()208 "(p7) br.cond.spnt.few 1b;;\n" in arch_write_lock_flags()
17 #define FEW(x...) macro20 #define FEW(x...) x macro70 FEW( ldr r2, [r0, #VLOCK_VOTING_OFFSET] )
9 destroyed just a few seconds ago. Since this file system can keep13 NILFS2 creates a number of checkpoints every few seconds or per
14 There are a few types of BCMA cores, they can be identified by30 Each BCMA core is identified by few fields, including class it
14 There are a few reasons why you might want to consider building your firmware21 Even if you have these needs there are a few reasons why you may not be
3 Microchip clock controller is consists of few oscillators, PLL, multiplexer4 and few divider modules.
9 few PLLs, and a level of mostly-generic clock generators sourcing from11 clock generators, but a few (like the ARM or HDMI) will source from
14 plus a few kilobytes for small objects. For example, if you want to reduce20 that is, 32K for windowBits=15 (default value) plus a few kilobytes
41 * detached. A few drivers need delayed work which must be cancelled before66 * A few drivers need to queue work which must be cancelled before driver
25 a few Nubus and all known Comm Slot Ethernet cards. If you have36 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
12 - There's a lot of complexity added past few years to make relocations faster.16 2. Any complexity added in this area past few years which can't be justified
18 1) Device with single USB LED and few physical ports24 2) Device with a physical port handled by few controllers
29 * Watch dmesg output for a few moments to see new dummy being allocated78 /* Check for expired dummies after a few new ones have been allocated */80 /* Dummies expire after a few cleanup instances */
71 Note: this section covers a few more aspects than the TL;DR and does things in130 suspend your efforts for a few days anyway. Whatever version you choose,154 issue. Always mention a few things: the latest kernel version you installed220 * Prepare yourself for the possibility that going through the next few steps254 A few words of general advice before digging into the details:359 to use good search terms; vary them a few times, too. While doing so try to518 followed by a few spaces and some letters.615 it. Quite a few programmers for example only care for just one driver, for695 Linux kernel development is completely driven by mail. Very few subsystems use768 quite a few other lists miss a way to search the archives. In those cases use a[all …]
14 /* Define a few things for the status register. We can use this to determine65 /* The second byte to the control register has a few special things.
5 This document describes a few common design patterns found in device drivers.16 While the kernel contains a few device drivers that assume that they will
36 bool "Limit USB device initialization to only a few retries"41 This option tells the kernel to make only a few retry attempts,
37 4. Otherwise, wait for a few milliseconds and see if THEIR_CLAIMS are released.38 5. If not, back off, release the claim and wait for a few more milliseconds.
