libnvme(2)

🌸 libnvme — enum nvme_id_ctrl_frmw 💅

okay bestie, welcome to the libnvme manual, section 2 of course — this one's all about one tiny lil enum and the way it tells you what a controller's firmware-update vibe is 💖

✨ NAME ✨

enum nvme_id_ctrl_frmw — the flags and values situation that spells out the capabilities around firmware updates, coming at you straight from &struct nvme_id_ctrl.frmw.

like. it's giving "firmware readiness report" and honestly? obsessed 🫶

---

✨ SYNOPSIS ✨

no cap, here's the whole thing, character for character:

enum nvme_id_ctrl_frmw {
    NVME_CTRL_FRMW_1ST_RO ,
    NVME_CTRL_FRMW_NR_SLOTS ,
    NVME_CTRL_FRMW_FW_ACT_NO_RESET ,
    NVME_CTRL_FRMW_MP_UP_DETECTION

};

she's short, she's sweet, she's iconic ✨

---

✨ Constants ✨

these are the besties. all four of them. no skipping 💀

• NVME_CTRL_FRMW_1ST_RO — when this bit is set, the first firmware slot is readonly. yeah. locked. can't touch. 🎀
• NVME_CTRL_FRMW_NR_SLOTS — this one's a mask, and what it does is pull out the number of firmware slots the controller can support. masking queen behavior fr fr 👑
• NVME_CTRL_FRMW_FW_ACT_NO_RESET — if this bit's set, the controller supports firmware activation without a reset. no restart era, we love to see it 🙈✨
• NVME_CTRL_FRMW_MP_UP_DETECTION — set bit means the controller can detect overlapping firmware/boot partition image update. like it'll notice. lowkey impressive ngl 🦋

pro tip from me to you bestie: those are flags in a bitfield, so please don't go comparing them raw like they're normal booleans. mask accordingly. love u 💜

---

and that's the whole page!! slay 🌈

this was the enum nvme_id_ctrl_frmw page from the API Manual for libnvme, section 2, dated July 2026. mwah. periodt. 🫶💖✨