ixgbe_erase_nvm_module(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ixgbe_erase_nvm_module(9) β€” the Kernel API Manual glow-up ✨

okay so bestie, welcome to the ixgbe_erase_nvm_module page from the Kernel API Manual β€” it's a kernel function, section 9, and it's literally about wiping an NVM module clean and then waiting for firmware to text back. iconic behavior honestly 🫢


✨ NAME ✨

ixgbe_erase_nvm_module β€” erase an NVM module and await firmware completion πŸ’«


🌸 SYNOPSIS 🌸

int ixgbe_erase_nvm_module (struct ixgbe_adapter *adapter , u16 module ,
       const char *component , struct netlink_ext_ack *extack );

that's the whole signature, no cap β€” copy it exactly, don't freestyle it πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • adapter β€” the PF data structure 🧚 like, the whole personality of this device right here
  • module β€” the module to erase πŸ‘‘ which one are we clearing out
  • component β€” name of the component being updated 🏷️ the label, for the record
  • extack β€” netlink extended ACK structure πŸ“¬ the messenger that carries the feedback back

πŸ¦‹ DESCRIPTION πŸ¦‹

So what does it actually do, you ask? It erases the inactive NVM bank associated with this module, and then it awaits a completion response message from firmware. like, it hits send and then it sits there with read receipts on, waiting for firmware to reply πŸ’€βœ¨

⚠️ Heads up bestie: this function assumes the caller has acquired the NVM resource. That's on you, not on it. no cap, don't skip that part πŸ™ˆ

⭐ RETURN ⭐

0 on success, or a negative error code on failure. that's it, that's the vibe check 🌈


πŸ’œ SEE ALSO πŸ’œ

Kernel file ./drivers/net/ethernet/intel/ixgbe/ixgbe_fw_update.c

the whole friend group, in order:

they're all linked, iykyk πŸ“


and that's the page!! source is ./drivers/net/ethernet/intel/i... and it's dated October 2026, so yeah β€” go erase that module, bestie, you've got this πŸ’…βœ¨πŸ‘‘

πŸ“¦ where this page comes from