Home
last modified time | relevance | path

Searched refs:ordering (Results 1 – 25 of 77) sorted by relevance

1234

/openbmc/u-boot/arch/arm/dts/
H A Dexynos54xx-pinctrl-uboot.dtsi10 * Replicate the ordering of arch/arm/include/asm/arch-exynos/gpio.h
11 * TODO(sjg@chromium.org): This ordering ceases to matter once GPIO
/openbmc/openbmc/meta-openembedded/meta-webserver/recipes-httpd/nginx/files/
H A D0001-Allow-the-overriding-of-the-endianness-via-the-confi.patch19 @@ -13,7 +13,13 @@ checking for system byte ordering
70 - echo "$0: error: cannot detect system byte ordering"
73 + echo "$0: error: cannot detect system byte ordering"
/openbmc/qemu/docs/system/
H A Dtarget-ppc.rst14 by the title text of each file, which isn't the same ordering
H A Dtargets.rst14 by the title text of each file, which isn't the same ordering
H A Dtarget-i386.rst11 by the title text of each file, which isn't the same ordering
/openbmc/openbmc/meta-phosphor/recipes-devtools/btrfs-tools/
H A Dbtrfs-tools_%.bbappend7 # There is an issue with the upstream `inherit_defer` ordering where a
/openbmc/qemu/target/ppc/translate/
H A Dmisc-impl.c.inc101 * eieio has complex semanitcs. It provides memory ordering between
119 * The end result is that CI memory ordering requires TCG_MO_ALL
120 * and it is not possible to special-case more relaxed ordering for
/openbmc/openbmc/poky/meta/recipes-support/apr/apr/
H A Dautoconf-2.73.patch1 To work with autoconf 2.73, tweak the macro ordering in configure.in.
/openbmc/openbmc/poky/meta/recipes-devtools/python/
H A Dpython3-sphinx_8.2.1.bb12 # The cache format of "{None, 'en', 'ja'}" doesn't seem to be consistent (dict ordering?)
/openbmc/openbmc/meta-ibm/recipes-bsp/u-boot/
H A Du-boot-aspeed-sdk_2019.04.bbappend10 # !!! Do not copy ibm-enterprise's use of little-endian key ordering !!!
/openbmc/u-boot/board/compulab/cm_t335/
H A Du-boot.lds84 * __bss_base and __bss_limit are for linker only (overlay ordering)
/openbmc/u-boot/board/birdland/bav335x/
H A Du-boot.lds88 * __bss_base and __bss_limit are for linker only (overlay ordering)
/openbmc/u-boot/board/cirrus/edb93xx/
H A Du-boot.lds87 * __bss_base and __bss_limit are for linker only (overlay ordering)
/openbmc/u-boot/arch/arm/mach-zynq/
H A Du-boot.lds107 * __bss_base and __bss_limit are for linker only (overlay ordering)
/openbmc/google-misc/
H A Dmeson.build40 # The ordering in this list intentionally lists dependencies higher than
/openbmc/openbmc-test-automation/redfish/
H A Dtest_xit.robot15 ${ERROR_REGEX} SEGV|core-dump|FAILURE|Failed to start|Found ordering cycle
/openbmc/openbmc/meta-openembedded/meta-initramfs/recipes-bsp/kexecboot/
H A Dkexecboot-cfg_0.2.bb41 # Default: 0 (lowest, ordered by device ordering)
/openbmc/qemu/target/i386/
H A Dhost-cpu.c177 xcc->ordering = 8; in host_cpu_class_init()
/openbmc/u-boot/arch/arm/cpu/armv7/
H A Dcache_v7_asm.S26 dmb @ ensure ordering with previous memory accesses
97 dmb @ ensure ordering with previous memory accesses
/openbmc/u-boot/board/vscom/baltos/
H A Du-boot.lds101 * __bss_base and __bss_limit are for linker only (overlay ordering)
/openbmc/openbmc/poky/meta-selftest/recipes-test/postinst/
H A Dpostinst_1.0.bb51 # written. This verifies the ordering between delayed postinsts.
/openbmc/u-boot/board/ti/am335x/
H A Du-boot.lds137 * __bss_base and __bss_limit are for linker only (overlay ordering)
/openbmc/qemu/docs/devel/
H A Dmulti-thread-tcg.rst255 ordered hosts needs to ensure things like store-after-load re-ordering
262 to enforce a particular ordering of memory operations from the point
272 provide explicit memory ordering semantics. However they can be used
279 This would enforce a strong load/store ordering so all loads/stores
284 also implicit memory ordering semantics which comes with each guest
H A Datomics.rst139 accesses, but do not otherwise impose any ordering on loads and
155 Restrictions to the ordering of accesses can also be specified
167 In other words, ``smp_rmb()`` puts a partial ordering on loads, but is not
175 In other words, ``smp_wmb()`` puts a partial ordering on stores, but is not
193 ``smp_mb()`` puts a partial ordering on both loads and stores. It is
307 in another thread, the ordering constraints propagates from the first to the
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libcereal/files/
H A D0001-cmake-Use-idirafter-instead-of-isystem.patch7 this exposes an interesting include ordering problem when using

1234