Searched full:around (Results 1 – 25 of 4092) sorted by relevance
12345678910>>...164
63 * 2AP. worked around in hardware66 * 4AP. worked around in hardware88 * 3AP. We work around this92 * 6AP. not affected - worked around in hardware93 * 7AP. not affected - worked around in hardware94 * 8AP. worked around in hardware - we get explicit CS errors if not98 * 10AP. not affected - worked around in hardware102 * 12AP. not affected - worked around in hardware103 * 13AP. not affected - worked around in hardware105 * 15AP. not affected - worked around in hardware[all …]
65 * 2AP. worked around in hardware68 * 4AP. worked around in hardware90 * 3AP. We work around this94 * 6AP. not affected - worked around in hardware95 * 7AP. not affected - worked around in hardware96 * 8AP. worked around in hardware - we get explicit CS errors if not100 * 10AP. not affected - worked around in hardware104 * 12AP. not affected - worked around in hardware105 * 13AP. not affected - worked around in hardware107 * 15AP. not affected - worked around in hardware[all …]
9 description: The datasheet claims this is based around a display controller29 usually around 3.0 V33 around 1.8 V43 maximum 300 ns minimum cycle which gives around 3 MHz max frequency
20 * around quickly. Locking rules (if necessary) have to be defined40 * cycle counter wrap around. Initialize with45 * more often than the cycle counter wraps around. The nanosecond46 * counter will only wrap around after ~585 years.
23 * To work around it we hide the relationship of the pointer and the object27 * RELOC_HIDE could trash r30. The bug can be worked around by changing53 * Adding an empty inline assembly before it works around the problem74 * Work around it via the same compiler barrier quirk that we used
99 * This function is intended to simplify locking around refcounting for102 * Operations on such objects require at least a read lock around103 * lookup + kref_get, and a write lock around kref_put + remove from lookup
34 * To work around it we hide the relationship of the pointer and the object38 * RELOC_HIDE could trash r30. The bug can be worked around by changing66 * Adding an empty inline assembly before it works around the problem95 * Work it around via a compiler barrier quirk suggested by Jakub Jelinek.
13 * Work around certain R4000 CPU errata (as implemented by GCC):39 * Work around certain R4400 CPU errata (as implemented by GCC):53 * Work around the "daddi" and "daddiu" CPU errata:
304 bool "Enable linker work around for PPC476FPE errata #46"306 This option enables a work around for an icache bug on 476311 The work around enables the appropriate linker options and313 page boundaries. The work around is only required when
314 bool "Enable linker work around for PPC476FPE errata #46"316 This option enables a work around for an icache bug on 476321 The work around enables the appropriate linker options and323 page boundaries. The work around is only required when
4 # only goes back to 1.6. So here's a wrapper layer to keep around for7 # We don't support 1.4 anymore, but we'll keep the wrappers around until
421 This option adds an alternative code sequence to work around Ampere444 This option adds an alternative code sequence to work around ARM466 This option adds an alternative code sequence to work around ARM488 This option adds an alternative code sequence to work around ARM511 This option adds an alternative code sequence to work around ARM532 This option adds an alternative code sequence to work around ARM551 This option adds an alternative code sequence to work around ARM588 This option adds an alternative code sequence to work around ARM703 Work around this by adding the affected CPUs to the list that needs736 Work around the erratum by triggering a dummy step exception[all …]
37 still be around and under development a decade from now.58 to get around a problem actually needs to become a generalized83 around.92 around. So it is always a good idea to remind reviewers of previously188 it with the assumption that you will not be around to maintain it208 eventually flow around you and get into the mainline anyway. In the Linux
9 * A function-like feature checking macro that is a wrapper around69 * A wrapper around the mutex implementation that allows perf to error check76 /* A wrapper around the condition variable implementation. */
5 * Work-around asm goto compiler bugs.23 * Work around these issues by adding a volatile inline asm with
20 compression ratio goes to around 2.7x while zbud's one is around 1.7x.
22 compression ratio goes to around 2.7x while zbud's one is around 1.7x.
20 development around the MPC86X processor families.30 development around the MPC885 processor family.119 to disable it if you have worked around the bug in the compiler
20 development around the MPC86X processor families.30 development around the MPC885 processor family.120 to disable it if you have worked around the bug in the compiler
43 bool "Dump user code around unhandled exception address"45 Enable this option to display user code around PC of the unhandled
71 some problem that could not be worked around.111 prescribed bus turn-around time116 prescribed bus turn-around time127 prescribed bus turn-around time. This error173 be worked around, such as a physical
68 some problem that could not be worked around.108 prescribed bus turn-around time113 prescribed bus turn-around time124 prescribed bus turn-around time. This error170 be worked around, such as a physical
196 /* Read didn't wrap around the buffer */ in saa7164_bus_set()254 /* Additional data wraps around the ring */ in saa7164_bus_set()350 /* Write doesn't wrap around the ring */ in saa7164_bus_get()353 /* Write wraps around the ring */ in saa7164_bus_get()409 /* Write doesn't wrap around the ring */ in saa7164_bus_get()412 /* Write wraps around the ring */ in saa7164_bus_get()439 /* Additional data wraps around the ring */ in saa7164_bus_get()