Home
last modified time | relevance | path

Searched full:stages (Results 1 – 25 of 107) sorted by relevance

12345

/openbmc/u-boot/include/dm/
H A Dutil.h46 * in the loader stages via special devicetree properties.
49 * are required in either SPL or TPL stages.
53 * SPL/TPL stages.
72 * in the loader stages via special devicetree properties.
75 * are required in either SPL or TPL stages.
79 * SPL/TPL stages.
/openbmc/qemu/.gitlab-ci.d/
H A Dstages.yml1 # Currently we have two build stages after our containers are built:
3 # - test (for test stages, using build artefacts from a build stage)
4 stages:
H A Dqemu-project.yml13 - local: '/.gitlab-ci.d/stages.yml'
/openbmc/pldm/oem/ibm/libpldmresponder/
H A Dplatform_oem_ibm.cpp36 using Stages = BootProgress::ProgressStages; in sendBiosAttributeUpdateEvent() typedef
37 auto currHostState = sdbusplus::message::convert_from_string<Stages>( in sendBiosAttributeUpdateEvent()
41 if (currHostState != Stages::SystemInitComplete && in sendBiosAttributeUpdateEvent()
42 currHostState != Stages::OSRunning && in sendBiosAttributeUpdateEvent()
43 currHostState != Stages::SystemSetup) in sendBiosAttributeUpdateEvent()
/openbmc/u-boot/include/
H A Dbootstage.h39 * A list of boot stages that we know about. Each of these indicates the
103 /* Boot stages related to loading a kernel from an IDE device */
118 /* Boot stages related to loading a kernel from an NAND device */
127 /* Boot stages related to loading a kernel from an network device */
140 * Boot stages related to loading a FIT image. Some of these are a
155 BOOTSTAGE_ID_FIT_RD_START = 120, /* Ramdisk stages */
158 BOOTSTAGE_ID_FIT_SETUP_START = 130, /* x86 setup stages */
168 * These boot stages are new, higher level, and not directly related
/openbmc/openbmc/meta-arm/meta-arm/classes/
H A Dsbsign.bbclass21 # stages. Instead they can call this function when needed by calling this function
/openbmc/pldm/platform-mc/
H A Ddbus_to_terminus_effecters.cpp198 using Stages = BootProgress::ProgressStages; in isHostOn() typedef
199 auto currHostState = sdbusplus::message::convert_from_string<Stages>( in isHostOn()
203 if (currHostState != Stages::SystemInitComplete && in isHostOn()
204 currHostState != Stages::OSRunning && in isHostOn()
205 currHostState != Stages::SystemSetup && in isHostOn()
206 currHostState != Stages::OEM) in isHostOn()
/openbmc/u-boot/arch/x86/include/asm/
H A Dpost.h12 /* post codes which represent various stages of init */
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-a/files/corstone1000/
H A D0002-fix-corstone1000-pass-spsr-value-explicitly.patch7 stages.
/openbmc/u-boot/arch/arm/lib/
H A Dcrt0_64.S18 * This file handles the target-independent stages of the U-Boot
35 * store any data which must be passed on to later stages. These
H A Dcrt0.S14 * This file handles the target-independent stages of the U-Boot
31 * store any data which must be passed on to later stages. These
H A Dspl.c32 * passed on to later stages. These data include the relocation destination,
/openbmc/u-boot/lib/efi/
H A DKconfig18 is useful for examining a platform in the early stages of porting
/openbmc/qemu/tests/migration-stress/guestperf/
H A Dcomparison.py29 # at various stages of iteration over RAM
59 # stages of the migration
/openbmc/libmctp/docs/
H A Dfuzzing.md6 will produce several build variants required for different fuzz engines/stages.
/openbmc/u-boot/doc/
H A DREADME.nand-boot-ppc44012 Here a short description of the different boot stages:
H A DREADME.multi-dtb-fit38 Uncompression and selection stages happen in fdtdec_setup() which is called
/openbmc/libpldm/docs/
H A Dfuzzing.md19 will produce several build variants required for different fuzz engines/stages.
/openbmc/openbmc/poky/bitbake/lib/bb/
H A Dprogress.py162 are two stages and the first takes 2s and the second takes
216 bb.warn('ProgressReporter: current stage beyond declared number of stages')
/openbmc/phosphor-ipmi-flash/tools/
H A Dupdater.cpp53 // Clean all active blobs to support multiple stages in updaterMain()
/openbmc/qemu/docs/devel/migration/
H A Ddirty-limit.rst59 After completing the three above stages, the throttle thread loops back
/openbmc/openbmc/meta-security/
H A D.gitlab-ci.yml17 stages:
/openbmc/u-boot/drivers/ddr/altera/
H A Dsequencer.h43 /* calibration stages */
/openbmc/openbmc/poky/documentation/kernel-dev/
H A Dconcepts-appx.rst16 requirements. Typically, the Linux kernel chosen is in the final stages
19 release. But, by being in the final stages of external development, the
21 the early stages of the Yocto Project development window.
/openbmc/u-boot/board/Seagate/nas220/
H A Dkwbimage.cfg42 # bit27-24: 8= CL+3, STARTBURST sample stages, for freqs 400MHz, unbuffered DIMM

12345