/openbmc/phosphor-ipmi-flash/bmc/firmware-handler/test/ |
H A D | firmware_json_unittest.cpp | 30 "preparation" : { in TEST() 58 "preparation" : { in TEST() 87 "preparation" : { in TEST() 116 "preparation" : { in TEST() 141 "preparation" : { in TEST() 210 "preparation" : { in TEST() 234 "preparation" : { in TEST() 256 "preparation" : { in TEST() 277 "preparation" : { in TEST() 317 "preparation" : { in TEST() [all …]
|
H A D | create_action_map.hpp | 17 actionPack->preparation = CreateTriggerMock(); in CreateActionMap()
|
H A D | firmware_multiplebundle_unittest.cpp | 77 bmcPack->preparation = std::move(bmcPrepareMock); in SetUp() 82 biosPack->preparation = std::move(biosPrepareMock); in SetUp()
|
H A D | firmware_state_notyetstarted_tarball_unittest.cpp | 44 actionPack->preparation = CreateTriggerMock(); in SetUp()
|
H A D | firmware_unittest.hpp | 56 actionPack->preparation = std::move(prepareMock); in SetUp()
|
/openbmc/phosphor-ipmi-flash/bmc/firmware-handler/ |
H A D | firmware_handlers_builder.cpp | 80 pack->preparation = std::move(buildSystemd(prep)); in buildHandlerFromJson() 84 pack->preparation = SkipAction::CreateSkipAction(); in buildHandlerFromJson()
|
H A D | config-static-bmc-reboot.json.in | 8 "preparation": { object
|
H A D | config-static-bmc.json.in | 8 "preparation": { object
|
H A D | config-static-bmc-with-update-status.json.in | 8 "preparation": { object
|
H A D | config-bios.json.in | 8 "preparation": { object
|
H A D | firmware_handler.hpp | 33 std::unique_ptr<TriggerableActionInterface> preparation; member
|
H A D | firmware_handler.cpp | 749 pack->preparation->trigger(); in changeState()
|
/openbmc/phosphor-ipmi-flash/ |
H A D | bmc_json_config.md | 30 "preparation": { 89 the BMC to receive the data. On a low memory BMC, the preparation step can be 94 - `preparation` 98 The `preparation`, `verification`, and `update` fields expect a `type` field, 102 In this configuration the `preparation` type is `systemd`. The `systemd` type 113 with the `preparation` action. 129 "preparation": { 163 "preparation": {
|
H A D | meson.build | 17 conf_data.set_quoted('PREPARATION_DBUS_SERVICE', get_option('preparation-dbus-service')) 21 conf_data.set_quoted('PREPARATION_BIOS_TARGET', get_option('preparation-bios-target'))
|
H A D | meson.options | 39 option('preparation-dbus-service', type : 'string', value : 'phosphor-ipmi-flash-bmc-prepare.target… 43 option('preparation-bios-target', type : 'string', value : 'phosphor-ipmi-flash-bios-prepare.target…
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | Xerox | 3 Use and copying of this software and preparation of derivative works based upon this software are p…
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/lvgl/files/ |
H A D | 0004-Factor-out-fbdev-initialization-code.patch | 8 preparation for addition of other backend initialization example
|
/openbmc/linux/Documentation/driver-api/mmc/ |
H A D | mmc-async-req.rst | 13 transfer, the DMA preparation overhead would not affect the MMC performance. 34 preparation may cost even more. As long as these slower preparations are run
|
/openbmc/linux/ |
H A D | Kbuild | 70 # A phony target that depends on all the preparation targets
|
/openbmc/phosphor-ipmi-flash/bmc/ |
H A D | README.md | 24 "preparation": {
|
/openbmc/qemu/docs/system/s390x/ |
H A D | protvirt.rst | 65 options -initrd and -cmdline are ineffective. The preparation of a PVM
|
/openbmc/u-boot/doc/ |
H A D | README.bloblist | 66 bloblist in preparation for the next stage. This involves adding a checksum so
|
H A D | README.vxworks | 60 application for VxWorks takes care of the kernel bootline preparation.
|
/openbmc/linux/Documentation/networking/ |
H A D | sfp-phylink.rst | 78 a separate preparation commit. 80 An older example of this preparation can be found in git commit
|
/openbmc/linux/tools/testing/memblock/ |
H A D | README | 25 skeleton of the memblock simulator")) and a few preparation commits just
|