Home
last modified time | relevance | path

Searched full:opening (Results 1 – 25 of 217) sorted by relevance

123456789

/openbmc/phosphor-ipmi-flash/tools/
H A Dupdater.cpp81 /* 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 Dp2a.cpp40 /** @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 Dzoned48 echo "(2) opening the first zone"
53 echo "opening the second zone"
58 echo "opening the last zone"
H A Dzoned.out23 (2) opening the first zone
27 opening the second zone
31 opening the last zone
/openbmc/phosphor-ipmi-flash/bmc/firmware-handler/
H A Dfirmware_handler.cpp283 * 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 DCVE-2024-38536.patch30 - SCLogDebug("Failed to append data while opening");
33 + SCLogDebug("Failed to append data while opening");
/openbmc/qemu/tests/qemu-iotests/
H A D1284 # 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 D065123 '''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 D09869 # There may be errors, but they should be fixed by opening the image
/openbmc/phosphor-dbus-interfaces/yaml/org/open_power/OCC/
H A DDevice.errors.yaml3 description: Opening OCC device failed.
/openbmc/qemu/target/i386/kvm/
H A Dvmsr_energy.c42 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 Dopusfile_0.12.bb1 DESCRIPTION = "Library for opening, seeking, and decoding opus audio files"
/openbmc/u-boot/tools/gdb/
H A Dgdbsend.c77 fprintf(stderr, "Opening file and reading image...\n"); in main()
98 fprintf(stderr, "Opening serial port and sending image...\n"); in main()
H A Dgdbcont.c54 fprintf(stderr, "Opening serial port and sending continue...\n"); in main()
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Configuration/
H A DGPIOValve.interface.yaml32 The name of the GPIO pin that controls opening the valve.
/openbmc/phosphor-ipmi-flash/bmc/firmware-handler/test/
H A Dfirmware_state_uploadinprogress_unittest.cpp48 /* 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 Dbug_report.md14 only. Please remove this section when opening a bug.
/openbmc/openpower-proc-control/
H A Dfiledescriptor.hpp28 * Creates a file descriptor by opening the device
/openbmc/entity-manager/schemas/
H A Dvalve.json26 "description": "The name of the GPIO pin that controls opening the valve.",
/openbmc/openbmc/poky/documentation/contributor-guide/
H A Dindex.rst11 If you run into an issue but don’t have a solution, opening a defect in
/openbmc/openpower-sbe-interface/
H A Dfile.hpp42 errMsg << "Opening the device with device path:" << devPath in FileDescriptor()
/openbmc/openbmc/poky/meta/recipes-connectivity/avahi/files/
H A D0001-Fix-opening-etc-resolv.conf-error.patch4 Subject: [PATCH] Fix opening /etc/resolv.conf error
/openbmc/openbmc-tools/dbus-vis/
H A Dmain.js22 true, // For opening file dialog from the renderer process
/openbmc/pyphosphor/obmc/dbuslib/
H A Dpropertycacher.py51 print("ERROR opening cache file: " + filename)
/openbmc/openbmc-tools/adcapp/src/
H A Dadcifc.h41 * adc through the adc manager (opening the device file, calling ioctl,

123456789