Home
last modified time | relevance | path

Searched full:relies (Results 1 – 25 of 189) sorted by relevance

12345678

/openbmc/qemu/docs/devel/
H A Dcontrol-flow-integrity.rst21 This type of CFI is entirely compiler-based and relies on the compiler knowing
60 As mentioned above, CFI is entirely compiler-based and therefore relies on
127 1. Fuzzing relies on the linker performing function wrapping at link-time.
130 2. Fuzzing also relies on a custom linker script, which is only supported by
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Network/Experimental/
H A DBond.interface.yaml79 This policy uses the same formula as layer2+3 but it relies on
85 This policy uses the same formula as layer3+4 but it relies on
/openbmc/phosphor-power/phosphor-regulators/test/
H A Dtest_utils.cpp2 // Meson runs clang-tidy directly on headers (.hpp), but the tool relies on
/openbmc/qemu/gdbstub/
H A Dmeson.build2 # The main gdbstub still relies on per-build definitions of various
/openbmc/qemu/.gitlab/issue_templates/
H A Dfeature_request.md4 Please note that QEMU, like most open source projects, relies on
/openbmc/openbmc/meta-openembedded/meta-gnome/recipes-gnome/grilo/
H A Dgrilo-plugins_0.3.16.bb18 # gnome-online-accounts requires opengl by default, so lua-factory PACKAGECONFIG relies on opengl b…
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/
H A D0029-corstone1000-enable-PSCI-reset.patch6 Even though corstone1000 does not implement entire PSCI APIs,it relies on
/openbmc/openbmc/poky/meta/recipes-core/initrdscripts/initramfs-framework/
H A Doverlayroot17 # It relies on the initramfs-module-rootfs to mount the original
25 # since it relies on it to mount the filesystem at initramfs startup
/openbmc/qemu/include/qapi/
H A Dopts-visitor.h27 * parser relies on strtoll() instead of strtoull(). Consequences:
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-m/files/corstone1000/psa-adac/
H A D0002-ADAC-Link-psa_interface-instead-of-tfm_sprt.patch11 tfm_hal_output_spm_log which relies on an SPM, which might not be
/openbmc/openbmc/poky/meta/recipes-support/dos2unix/
H A Ddos2unix_7.5.2.bb20 # The dos2unix NLS relies on po4a-native, while po4a recipe is
/openbmc/openbmc/poky/meta/recipes-devtools/gdb/gdb/
H A D0001-mips-linux-nat-Define-_ABIO32-if-not-defined.patch26 +/* musl does not define and relies on compiler built-in macros for it */
/openbmc/qemu/tests/tcg/multiarch/
H A Dsigreturn-sigmask.c4 * Then sigwait() SIGUSR2, which relies on it remaining blocked.
/openbmc/u-boot/doc/device-tree-bindings/sysreset/
H A Dti,sci-sysreset.txt14 which is managed by the SYSFW. Because this relies on the TI SCI protocol
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse/
H A Da1d58ae1be99571a88b8439b027abe6349b74658.patch24 # relies on tests running sequential (i.e., don't dare to use e.g. the xdist
/openbmc/openbmc/meta-arm/meta-arm/recipes-security/optee/optee-os/
H A D0003-optee-enable-clang-support.patch29 # Core ASLR relies on the executable being ready to run from its preferred load
/openbmc/u-boot/drivers/timer/
H A Driscv_timer.c7 * This driver relies on RISC-V platform codes to provide the essential API
/openbmc/phosphor-power/phosphor-regulators/docs/
H A Dtesting.md42 The mock framework typically relies on a class hierarchy of the following form:
/openbmc/phosphor-power/phosphor-power-sequencer/docs/
H A Dtesting.md42 The mock framework typically relies on a class hierarchy of the following form:
/openbmc/u-boot/api/
H A DREADME24 for example it doesn't keep states, but relies on hints from the app and
/openbmc/qemu/docs/system/devices/
H A Divshmem-flat.rst20 ivshmem.rst for more details). It relies on the ivshmem server to create and
/openbmc/u-boot/doc/device-tree-bindings/power/
H A Dti,sci-pm-domain.txt14 this relies on the TI SCI protocol to communicate with the SYSFW it must be a
/openbmc/u-boot/doc/
H A DREADME.boston30 with support for the CPS features the Boston board relies upon. You will
/openbmc/openpower-vpd-parser/
H A DREADME.md31 - It relies on a runtime JSON configuration (see examples/inventory.json) to
/openbmc/docs/
H A Dmeta-layer-guidelines.md116 - Relies on or implements on OpenBMC defined Dbus interfaces.
118 - Relies on OpenBMC specific layouts, configuration information to accomplish

12345678