| /openbmc/openbmc-test-automation/ipmi/ |
| H A D | test_ipmi_sel.robot | 242 Verify Reservation ID Erasure Status
243 …[Documentation] Verify Erasure status by clearing SEL with Reserve ID and verify the response byt…
244 ... whether erasure status is updated in clear sel command response data using new Reserve ID.
267 # Check the Erasure status of Clear SEL.
270 # 00 - Erasure in Progress , 01 - Erasure Complete.
|
| /openbmc/u-boot/drivers/mtd/ubi/ |
| H A D | wl.c | 22 * 'ubi_wl_put_peb()' function, they are scheduled for erasure. The erasure is
610 dbg_wl("schedule erasure of PEB %d, EC %d, torture %d", in schedule_erase()
893 * erasure.
909 * have been changed, schedule it for erasure.
1070 dbg_wl("cancel erasure of PEB %d EC %d", pnum, e->ec);
1107 /* Re-schedule the LEB for erasure */
1120 * this physical eraseblock for erasure again would cause
1216 * be moved. It will be scheduled for erasure in the
1234 * and should be scheduled for erasure.
|
| H A D | io.c | 305 * erase_callback - MTD erasure call-back.
365 ubi_err(ubi, "interrupted PEB %d erasure", pnum); in do_sync_erase()
472 * nor_erase_prepare - prepare a NOR flash PEB for erasure.
476 * NOR flash, or at least some of them, have peculiar embedded PEB erasure
557 * if the erasure failed or the torturing test failed, and other negative error
|
| H A D | ubi-media.h | 194 * erasure, then L is written to,i.e. mapped to another physical eraseblock P1,
211 * the copying). Moreover, the unclean reboot may happen when the erasure of P
|
| H A D | attach.c | 48 * PEBs in the @erase list are scheduled for erasure later.
929 * be a result of power cut during erasure. in scan_peb()
940 * operation. So we just schedule this PEB for erasure. in scan_peb()
943 * corrupt both headers because NOR flash erasure is in scan_peb()
|
| H A D | ubi.h | 752 * @vol_id: the volume ID on which this erasure is being performed
766 /* The below fields are only relevant to erasure works */
|
| H A D | kapi.c | 637 * corresponding physical eraseblock for erasure, so that it will eventually be
|
| H A D | eba.c | 313 * physical eraseblock for erasure. Returns zero in case of success and a
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/google/gbmc/ |
| H A D | Hoth.interface.yaml | 107 Initiates erasure of the EEPROM staging area. Note that this will lock
|
| /openbmc/u-boot/include/mtd/ |
| H A D | ubi-user.h | 104 * schedules corresponding physical eraseblock for erasure, and returns. Unlike
178 /* LEB erasure command, used for debugging, disabled by default */
|
| /openbmc/phosphor-host-ipmid/ |
| H A D | storagehandler.cpp | 490 * Erasure status cannot be fetched from DBUS, so always return erasure in clearSEL()
|
| /openbmc/qemu/hw/ipmi/ |
| H A D | ipmi_bmc_sim.c | 1401 rsp_buffer_push(rsp, 1); /* Erasure complete */ in clear_sdr_rep()
1404 rsp_buffer_push(rsp, 1); /* Erasure complete */ in clear_sdr_rep()
1604 rsp_buffer_push(rsp, 1); /* Erasure complete */ in clear_sel()
1607 rsp_buffer_push(rsp, 1); /* Erasure complete */ in clear_sel()
|
| /openbmc/intel-ipmi-oem/src/ |
| H A D | storagecommands.cpp | 1105 // Erasure status cannot be fetched, so always return erasure status as in ipmiStorageClearSEL()
|
| /openbmc/phosphor-host-ipmid/dbus-sdr/ |
| H A D | storagecommands.cpp | 1164 // Erasure status cannot be fetched, so always return erasure status as in ipmiStorageClearSEL()
|
| /openbmc/ipmitool/lib/ |
| H A D | ipmi_sdradd.c | 217 printf("Wait for SDRR erasure completed...\n"); in ipmi_sdr_repo_clear()
|
| /openbmc/fb-ipmi-oem/src/ |
| H A D | selcommands.cpp | 1689 /* Erasure status cannot be fetched, so always return erasure in ipmiStorageClearSEL()
|
| /openbmc/qemu/hw/block/ |
| H A D | pflash_cfi02.c | 200 * erasure based on CFI address 0x21 which is "Typical timeout per individual
|
| /openbmc/u-boot/fs/yaffs2/ |
| H A D | yaffs_guts.c | 2341 "**>> Erasure failed %d", block_no); in yaffs_block_became_dirty()
2345 /* Verify erasure if needed */ in yaffs_block_became_dirty()
2353 ">>Block %d erasure supposedly OK, but chunk %d not erased", in yaffs_block_became_dirty()
2963 * If the whole block became dirty, this will kick off an erasure. in yaffs_chunk_del()
|
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | openbmc.json | 643 …"Message": "Intel ME has encountered an error during Flash erasure procedure probably due to Flash…
|
| H A D | openbmc_message_registry.hpp | 898 …"Intel ME has encountered an error during Flash erasure procedure probably due to Flash part corru…
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | Volume_v1.xml | 383 …ion" String="The volume will be available for use immediately, with data erasure and preparation t…
386 …<Annotation Term="OData.Description" String="Data erasure and preparation tasks will complete befo…
|
| /openbmc/u-boot/drivers/mtd/spi/ |
| H A D | spi-nor-core.c | 604 * Initiate the erasure of a single sector
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | ComputerSystem.v1_25_0.json | 1144 … "description": "Ensure secure erasure of all devices and fail the request if not possible.",
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | ComputerSystem.v1_25_0.json | 1144 … "description": "Ensure secure erasure of all devices and fail the request if not possible.",
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
| H A D | ComputerSystem_v1.xml | 250 …<Annotation Term="OData.Description" String="Ensure secure erasure of all devices and fail the req…
|