__i40e_read_nvm_word(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __i40e_read_nvm_word β€” Kernel API Manual, but make it make sense πŸŽ€

okay bestie, welcome to the <pink>Kernel API Manual</pink> page for __i40e_read_nvm_word(9) β€” yes the double-underscore one, she's special, she's internal, she has lore πŸ’œ


✨ NAME ✨

__i40e_read_nvm_word β€” reads an nvm word, and assumes the caller does the locking πŸ”’ like fr fr it is trusting you to have handled that already


🌸 SYNOPSIS 🌸

int __i40e_read_nvm_word (struct i40e_hw *hw , u16 offset , u16 *data );

like it returns an int, takes three things, that's the whole vibe ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • hw β€” pointer to the HW structure πŸ’– you know, the hardware bestie
  • offset β€” offset of the Shadow RAM word to read (0x000000 - 0x001FFF) 🎯 note the range, she has boundaries
  • data β€” word read from the Shadow RAM πŸ“ this is where the good stuff lands

πŸ‘‘ DESCRIPTION πŸ‘‘

so basically it reads one 16 bit word from the Shadow RAM. one. singular. a little 16-bit snack 🧚✨

⚠️ Do not use this function except in cases where the nvm lock is already taken via i40e_acquire_nvm. like. seriously. this is the whole point of the __. the lock is your job, not hers 😭 no cap, if you call this without the lock you're on your own and it's not giving responsible engineering πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/net/ethernet/intel/i40e/i40e_nvm.c β€” the mothership πŸ›Έ

and the whole friend group, alphabetically-ish, all of them, no one left out 🫢

like. that's the entire contact list. she's connected 🌈


okay that's the page, ily, go take that lock first πŸ’…βœ¨

this lil manual moment came from ./drivers/net/ethernet/intel/i40e and it's dated October 2026 β€” so, era-defining honestly πŸ‘‘πŸ«Ά go forth and read that nvm word πŸŽ€

πŸ“¦ where this page comes from