ixgbe_write_nvm_module(9)

💅 ixgbe_write_nvm_module — the kernel API manual, bestie edition ✨

okay so real talk, this is a page from the Kernel API Manual, and today's main character is ixgbe_write_nvm_module(9). she writes data to an NVM module. that's it, that's the vibe. let's get into it 🎀

---

✨ NAME ✨

ixgbe_write_nvm_module — write data to an NVM module 🦋

---

🌸 SYNOPSIS 🌸

int ixgbe_write_nvm_module (struct ixgbe_adapter *adapter , u16 module ,
       const char *component , const u8 *image , u32 length , struct
       netlink_ext_ack *extack );

like, that's the whole call signature, copied exactly, no notes 💅

---

🫶 ARGUMENTS 🫶

• adapter — the PF driver structure. the whole personality of this call tbh.
• module — the module id to program. which one are we doing? this tells us 🔥
• component — the name of the component being updated. name drop, periodt.
• image — buffer of image data to write to the NVM. the actual bytes, the moment, the ~content~.
• length — length of the buffer. how much of that image we're actually taking, no cap.
• extack — netlink extended ACK structure. the receipts structure, fr fr.

---

💖 DESCRIPTION 💖

so what she does is: loop over the data for a given NVM module and program it in 4 Kb blocks. yes bestie, blocks. and after each block is programmed, she notifies devlink core of progress — so everyone in the group chat knows how far along we are 😭👑

then (and yes this is said again, she's thorough): she loops over a block of data and programs the NVM in 4k block chunks. iconic of her to restate it ngl.

⚠️ okay this is the important one: this function assumes the caller has acquired the NVM resource. that's on you, not on her. she will not be checking. do not come for her if you skipped that step 🙈

---

⭐ RETURN ⭐

0 on success, or a negative error code on failure. slay or don't slay, there's no in between 💀

---

🌈 SEE ALSO 🌈

kernel file: ./drivers/net/ethernet/intel/ixgbe/ixgbe_fw_update.c

and the whole friend group, in order, exactly as listed:

• ixgbe_send_package_data(9)
• ixgbe_check_component_response(9)
• ixgbe_send_component_table(9)
• ixgbe_write_one_nvm_block(9)
• ixgbe_erase_nvm_module(9)
• ixgbe_switch_flash_banks(9)
• ixgbe_flash_component(9)
• ixgbe_finalize_update(9)
• ixgbe_get_pending_updates(9)
• ixgbe_cancel_pending_update(9)
• ixgbe_flash_pldm_image(9)

---

and that's the page!! 🎀 source path is ./drivers/net/ethernet/intel/i... (truncated by the terminal, not by me, blame the rendering 💅), dated October 2026, and the page itself is ixgbe_write_nvm_module(9). mwah, go write some NVM blocks responsibly, ily 🫶✨