/openbmc/qemu/docs/devel/ |
H A D | tcg-icount.rst | 12 with cycle accurate emulation - QEMU does not attempt to emulate how 57 up to date and accurate reading of the icount number. 71 correct and accurate clock. IO port instructions and accesses to
|
/openbmc/u-boot/test/py/tests/ |
H A D | test_sleep.py | 11 # Setup env__sleep_accurate to False if time is not accurate on your platform 22 pytest.skip('sleep is not accurate')
|
/openbmc/linux/arch/x86/math-emu/ |
H A D | README | 74 a value of pi which is accurate to more than 128 bits. As a consequence, 75 the reduced argument is accurate to more than 64 bits for arguments up 76 to a few pi, and accurate to more than 64 bits for most arguments, 78 80486, which uses a value of pi which is accurate to 66 bits. 243 accurate to 64 bits can result in a relative accuracy in cos() of 273 for pi which is accurate to more than 128 bits precision. As a 299 pi/2) the emulator is more accurate than an 80486 FPU. For very large 300 arguments, the emulator is far more accurate. 317 results which are in error (i.e. less accurate than the best possible
|
/openbmc/linux/include/linux/platform_data/ |
H A D | davinci_asp.h | 40 * and makes clock more accurate (FS is not symmetrical and the 59 * ACCURATE CLOCK APPROACH:
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/geoip/ |
H A D | geoip_1.6.12.bb | 4 accurate as of March 2003. This database simply contains IP blocks as keys, and \ 5 countries as values. This database should be more complete and accurate than \
|
/openbmc/linux/arch/sh/kernel/ |
H A D | unwinder.c | 10 * the most accurate unwinder being the currently active one. 26 * construct more accurate stack traces.
|
/openbmc/linux/scripts/ksymoops/ |
H A D | README | 5 other utilities in order to give more accurate Oops debugging.
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/usleep/files/ |
H A D | usleep.1 | 20 Probably not accurate on many machines down to the microsecond. Count
|
/openbmc/linux/include/linux/ |
H A D | getcpu.h | 14 If you want 100% accurate information pass NULL instead. */
|
/openbmc/linux/drivers/hte/ |
H A D | Kconfig | 9 benefit for the applications needing accurate timestamping event with
|
/openbmc/linux/arch/powerpc/include/asm/ |
H A D | accounting.h | 9 /* Stuff for accurate time accounting */
|
/openbmc/u-boot/post/lib_powerpc/fpu/ |
H A D | 980619-1.c | 34 /* Assumes ieee754 accurate arithmetic above. */ in fpu_post_test_math4()
|
/openbmc/linux/arch/arm64/include/asm/ |
H A D | asm-prototypes.h | 28 * this prototype is not entirely accurate.
|
/openbmc/linux/Documentation/hwmon/ |
H A D | tmp102.rst | 23 sensor is accurate to 0.5 degree over the range of -25 to +85 C, and to 1.0
|
H A D | tmp108.rst | 26 The sensor is accurate to 0.75C over the range of -25 to +85 C, and to 1.0
|
/openbmc/linux/Documentation/networking/ |
H A D | xfrm_sync.rst | 15 the processing of the SA as accurate as possible if it has access to it. 18 These patches add ability to sync and have accurate lifetime byte (to
|
/openbmc/linux/arch/sh/include/uapi/asm/ |
H A D | cpu-features.h | 11 * reasonably accurate.
|
/openbmc/linux/Documentation/mm/damon/ |
H A D | index.rst | 11 - *accurate* (the monitoring output is useful enough for DRAM level memory
|
/openbmc/linux/Documentation/accounting/ |
H A D | psi.rst | 13 Without an accurate measure of such contention, users are forced to 22 Having an accurate measure of productivity losses caused by resource
|
/openbmc/linux/arch/arm64/lib/ |
H A D | strlen.S | 116 loop with the accurate NUL check. */ 137 /* The fast check failed, so do the slower, accurate NUL check. */
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-crypto/libtomcrypt/ |
H A D | libtomcrypt_1.18.2.bb | 4 # Unlicense isn't very accurate for this revision, it was WTFPL in 0.18.0-rc1:
|
/openbmc/linux/drivers/thermal/ti-soc-thermal/ |
H A D | Kconfig | 32 this generation are not accurate, nor they are very close to
|
/openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/templates/ |
H A D | recipedetails.html | 124 … from previous builds and from parsing layers, so we can never be sure it is 100% accurate"></span> 129 … is based on information from previous builds, so we can never be sure it is 100% accurate"></span>
|
/openbmc/linux/Documentation/sound/soc/ |
H A D | clocking.rst | 43 audio clocks as it usually gives more accurate sample rates than the CPU.
|
/openbmc/linux/Documentation/translations/ |
H A D | index.rst | 50 Translations try to be as accurate as possible but it is not possible to map
|