/openbmc/phosphor-ipmi-flash/tools/ |
H A D | updater.cpp | 81 /* Trigger the verification by opening and committing the verify file. in updaterMain() 83 std::fprintf(stderr, "Opening the verification file\n"); in updaterMain() 94 /* Trigger the update by opening and committing the update file. */ in updaterMain() 95 std::fprintf(stderr, "Opening the update file\n"); in updaterMain()
|
H A D | p2a.cpp | 40 /** @brief RAII wrapper and its destructor for opening a file descriptor */ 92 std::format("Error opening file '{}'", input)); in sendContents()
|
/openbmc/qemu/tests/qemu-iotests/tests/ |
H A D | zoned | 48 echo "(2) opening the first zone" 53 echo "opening the second zone" 58 echo "opening the last zone"
|
H A D | zoned.out | 23 (2) opening the first zone 27 opening the second zone 31 opening the last zone
|
/openbmc/phosphor-ipmi-flash/bmc/firmware-handler/ |
H A D | firmware_handler.cpp | 283 * still have the flash image blob_id open will fail. Opening the flash 292 * re-opening the image, and if we have the image open, we don't allow in open() 293 * opening the hash. This design decision may be re-evaluated, and changed in open() 310 /* 2a) are they opening the active image? this can only happen if they in open() 313 /* 2b) are they opening the active hash? this can only happen if they in open() 340 /* Handle opening the verifyBlobId --> we know the image and hash in open() 386 * opening the one they already opened during this update sequence, or it's in open() 387 * the first time they're opening it. in open() 391 /* If they're not opening the hashBlobId they must be opening a firmware in open() 404 * now they're opening /flash/bios without finishing out in open() [all …]
|
/openbmc/openbmc/meta-security/recipes-ids/suricata/files/ |
H A D | CVE-2024-38536.patch | 30 - SCLogDebug("Failed to append data while opening"); 33 + SCLogDebug("Failed to append data while opening");
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 128 | 4 # Test that opening O_DIRECT succeeds when image file I/O produces EIO 82 # Opening image should succeed but the read operation should fail
|
H A D | 065 | 123 '''Testing a qcow2 version 3 image with lazy refcounts disabled, opening 133 '''Testing a qcow2 version 3 image with lazy refcounts enabled, opening
|
H A D | 098 | 69 # There may be errors, but they should be fixed by opening the image
|
/openbmc/phosphor-dbus-interfaces/yaml/org/open_power/OCC/ |
H A D | Device.errors.yaml | 3 description: Opening OCC device failed.
|
/openbmc/qemu/target/i386/kvm/ |
H A D | vmsr_energy.c | 42 error_report("Error opening %s", path); in is_rapl_enabled() 133 error_report("Error opening physical_package_id file"); in vmsr_get_max_physical_package() 263 error_report("Error opening %s", path_name); in vmsr_read_thread_stat() 288 error_report("Error opening /proc/qemu/task"); in vmsr_get_thread_ids()
|
/openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/opusfile/ |
H A D | opusfile_0.12.bb | 1 DESCRIPTION = "Library for opening, seeking, and decoding opus audio files"
|
/openbmc/u-boot/tools/gdb/ |
H A D | gdbsend.c | 77 fprintf(stderr, "Opening file and reading image...\n"); in main() 98 fprintf(stderr, "Opening serial port and sending image...\n"); in main()
|
H A D | gdbcont.c | 54 fprintf(stderr, "Opening serial port and sending continue...\n"); in main()
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Configuration/ |
H A D | GPIOValve.interface.yaml | 32 The name of the GPIO pin that controls opening the valve.
|
/openbmc/phosphor-ipmi-flash/bmc/firmware-handler/test/ |
H A D | firmware_state_uploadinprogress_unittest.cpp | 48 /* Opening the image file will add the active image blob id */ in TEST_F() 58 /* Opening the image file will add the active image blob id */ in TEST_F() 169 * NOTE: Re-opening /flash/image will transition back to uploadInProgress, but
|
/openbmc/openbmc/.github/ISSUE_TEMPLATE/ |
H A D | bug_report.md | 14 only. Please remove this section when opening a bug.
|
/openbmc/openpower-proc-control/ |
H A D | filedescriptor.hpp | 28 * Creates a file descriptor by opening the device
|
/openbmc/entity-manager/schemas/ |
H A D | valve.json | 26 "description": "The name of the GPIO pin that controls opening the valve.",
|
/openbmc/openbmc/poky/documentation/contributor-guide/ |
H A D | index.rst | 11 If you run into an issue but don’t have a solution, opening a defect in
|
/openbmc/openpower-sbe-interface/ |
H A D | file.hpp | 42 errMsg << "Opening the device with device path:" << devPath in FileDescriptor()
|
/openbmc/openbmc/poky/meta/recipes-connectivity/avahi/files/ |
H A D | 0001-Fix-opening-etc-resolv.conf-error.patch | 4 Subject: [PATCH] Fix opening /etc/resolv.conf error
|
/openbmc/openbmc-tools/dbus-vis/ |
H A D | main.js | 22 true, // For opening file dialog from the renderer process
|
/openbmc/pyphosphor/obmc/dbuslib/ |
H A D | propertycacher.py | 51 print("ERROR opening cache file: " + filename)
|
/openbmc/openbmc-tools/adcapp/src/ |
H A D | adcifc.h | 41 * adc through the adc manager (opening the device file, calling ioctl,
|