Home
last modified time | relevance | path

Searched full:involves (Results 1 – 25 of 96) sorted by relevance

1234

/openbmc/bmcweb/redfish-core/include/registries/
H A Dopenbmc_message_registry.readmefirst.md10 this involves not using terms like "CPU", "Drive", "Backplane", etc in the
20 This generally involves placing the substitution parameters in the
/openbmc/openbmc/meta-ampere/meta-common/recipes-phosphor/watchdog/
H A Dphosphor-watchdog_%.bbappend4 # Ampere Mt. Jade power control involves different action during
/openbmc/openpower-hw-diags/analyzer/
H A Dutil.hpp5 * stuff that involves libhei).
/openbmc/openbmc/poky/meta/recipes-devtools/valgrind/valgrind/
H A D0001-docs-Disable-manual-validation.patch6 validating manual and manpages, this task involves calling xmllint which
/openbmc/openbmc/poky/meta/classes-recipe/
H A Dcmake-qemu.bbclass7 # involves a certain risk, which is also the reason why this feature
/openbmc/qemu/python/
H A DPACKAGE.rst24 <https://wiki.qemu.org/Contribute/SubmitAPatch>`_, which involves
/openbmc/u-boot/doc/driver-model/
H A Dserial-howto.txt36 this involves these steps:
H A Di2c-howto.txt46 this involves these steps:
H A Dlivetree.txt35 the parent of a node is a slow process. Reading from nodes involves a
236 Adding a new function for device-tree access involves the following steps:
/openbmc/qemu/tests/tcg/x86_64/
H A Dcross-modifying-code.c8 * involves patching the first byte with int3.
/openbmc/qemu/docs/system/arm/
H A Dimx8mp-evk.rst38 of writing and involves two steps. First run the following commands in the
/openbmc/u-boot/doc/
H A DREADME.i2c15 minimal overhead and involves very little code. The scheme can survive
H A DREADME.bloblist66 bloblist in preparation for the next stage. This involves adding a checksum so
/openbmc/u-boot/arch/arm/include/asm/arch-mx7/
H A Dmx7_plugin.S91 * "image_copy_start", which involves FLASH_OFFSET, plus the first
/openbmc/qemu/tests/qemu-iotests/
H A D13061 # bdrv_make_empty() involves a header update for qcow2
H A D31035 # The difference is that this test case involves a bottom node to the
/openbmc/u-boot/arch/sandbox/include/asm/
H A Du-boot-sandbox.h66 * Since address mapping involves calling every driver, provide a way to
/openbmc/phosphor-net-ipmid/sol/
H A Dsol_manager.hpp197 * Starting a payload instance involves creating the context object,
209 * Stopping a payload instance involves stopping and removing the
/openbmc/qemu/docs/specs/
H A Dppc-spapr-uv-hcalls.rst23 Switching to SVM mode involves a number of hcalls issued by the ultravisor to
/openbmc/qemu/docs/devel/migration/
H A Ddirty-limit.rst35 CALCULATE(2), as the name implies. It involves preparing the dirty
/openbmc/u-boot/arch/arm/include/asm/arch-mx6/
H A Dmx6_plugin.S139 * "image_copy_start", which involves FLASH_OFFSET, plus the first
/openbmc/docs/testing/
H A Drun-test-docker.md3 Running OpenBMC automation using Docker involves creating a Docker image and
/openbmc/docs/designs/
H A Dsol-sysrq.md29 OpenBMC SOL involves several ways:
/openbmc/docs/
H A Dyocto-development.md16 The first is the easy case, and largely involves picking the system
/openbmc/openbmc/poky/documentation/dev-manual/
H A Dgobject-introspection.rst40 library package involves the following:

1234