e1000e_acquire_nvm(9)

💅 e1000e_acquire_nvm(9) — like, the Kernel API Manual era 🎀

okay so bestie, welcome to the Kernel API Manual page for e1000e_acquire_nvm(9) — yes that's the whole title, we're being formal today ✨

---

🌸 NAME 🌸

e1000e_acquire_nvm — the generic "hey can I pls have the EEPROM" request 🫶

✨ SYNOPSIS ✨

s32 e1000e_acquire_nvm (struct e1000_hw *hw );

🦋 ARGUMENTS 🦋

• hw — pointer to the HW structure 💖 literally just a pointer to the hardware struct, that's the whole vibe

👑 DESCRIPTION 👑

okay so here's the tea 🍓: this function sets the EEPROM access request bit and then waits for the EEPROM access grant bit. It's giving "asking permission and then standing there politely until the answer comes back."

If the access grant bit gets set — slay, it returns successful 💅

If it does not get set — not the vibe 😭 — it clears the request for EEPROM access and returns -E1000_ERR_NVM (-1). No cap, that's the error, and it's -1, and yes those are the same number, don't come for me.

fr fr, remember: no grant = clear the request bit AND return -E1000_ERR_NVM (-1). Two things. Both of them. Periodt. 🔥

🌈 SEE ALSO 🌈

Kernel file ./drivers/net/ethernet/intel/e1000e/nvm.c — that's where she lives 🏠

and the whole friend group, in this exact order, because we do not skip anyone at this table 🫶:

• e1000_raise_eec_clk(9)
• e1000_lower_eec_clk(9)
• e1000_shift_out_eec_bits(9)
• e1000_shift_in_eec_bits(9)
• e1000e_poll_eerd_eewr_done(9)
• e1000_standby_nvm(9)
• e1000_stop_nvm(9)
• e1000e_release_nvm(9)
• e1000_ready_nvm_eeprom(9)
• e1000e_read_nvm_eerd(9)
• e1000e_write_nvm_spi(9)
• e1000_read_pba_string_generic(9)
• e1000_read_mac_addr_generic(9)
• e1000e_validate_nvm_checksum_generic(9)
• e1000e_update_nvm_checksum_generic(9)
• e1000e_reload_nvm_generic(9)

---

and that's the page, bestie 🧚💜 — brought to you by the source ./drivers/net/ethernet/intel/e... and dated October 2026, signing off as e1000e_acquire_nvm(9) one last time because the footer said so and we respect the footer 💀🎀