libnvme(9)

📦 version 3.2, in arch rolling

💖 NAME 💖

okay so bestie, this is the libnvme(9) manual page, and the main character is enum nvme_fw_commit_ca — literally the Firmware Commit - Commit Action enum. it's giving firmware-commit choices, and we are going through every single constant, no skipping. 🎀

✨ SYNOPSIS ✨

here's the enum in all its glory:

enum nvme_fw_commit_ca {
    NVME_FW_COMMIT_CA_REPLACE ,
    NVME_FW_COMMIT_CA_REPLACE_AND_ACTIVATE ,
    NVME_FW_COMMIT_CA_SET_ACTIVE ,
    NVME_FW_COMMIT_CA_REPLACE_AND_ACTIVATE_IMMEDIATE ,
    NVME_FW_COMMIT_CA_REPLACE_BOOT_PARTITION ,
    NVME_FW_COMMIT_CA_ACTIVATE_BOOT_PARTITION

};

🌸 Constants 🌸

these are the constants, and yes, every one matters:

  • NVME_FW_COMMIT_CA_REPLACE — the downloaded image replaces the existing image, if any, in the specified Firmware Slot. the newly placed image is not activated. no cap, it just sits there. 💅
  • NVME_FW_COMMIT_CA_REPLACE_AND_ACTIVATE — the downloaded image replaces the existing image, if any, in the specified Firmware Slot. then the newly placed image is activated at the next Controller Level Reset. slay. ✨
  • NVME_FW_COMMIT_CA_SET_ACTIVE — no new image swap here; the existing image in the specified Firmware Slot is activated at the next Controller Level Reset. iconic. 🔥
  • NVME_FW_COMMIT_CA_REPLACE_AND_ACTIVATE_IMMEDIATE — the downloaded image replaces the existing image, if any, in the specified Firmware Slot and is then activated immediately. and if there is not a newly downloaded image, then the existing image in the specified firmware slot is activated immediately. periodt. 💀
  • NVME_FW_COMMIT_CA_REPLACE_BOOT_PARTITION — the downloaded image replaces the Boot Partition specified by the Boot Partition ID field. 🦋
  • NVME_FW_COMMIT_CA_ACTIVATE_BOOT_PARTITION — mark the Boot Partition specified in the BPID field as active and update BPINFO.ABPID. iykyk. 👑
🎀 sign-off bestie: this page is from enum nvme_fw_commit_ca in the libnvme(9) manual, dated October 2026. mwah 💋
📦 where this page comes from