igb_write_nvm_srwr_i210(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– igb_write_nvm_srwr_i210(9) πŸ’–

okay bestie, welcome to the Kernel API Manual page for igb_write_nvm_srwr_i210(9) β€” yes, we're doing kernel-function glow-up energy, and this one is all about writing to Shadow RAM. 🫢

✨ NAME ✨

igb_write_nvm_srwr_i210 β€” Write to Shadow RAM using EEWR.

πŸ¦‹ SYNOPSIS πŸ¦‹

s32 igb_write_nvm_srwr_i210 (struct e1000_hw *hw , u16 offset , u16 words , u16 *data );

πŸŽ€ ARGUMENTS πŸŽ€

  • hw β€” pointer to the HW structure. like, the hardware bestie we're handing over.
  • offset β€” offset within the Shadow RAM to be written to. know exactly where we're dropping the data.
  • words β€” number of words to write. count 'em.
  • data β€” 16 bit word(s) to be written to the Shadow RAM. the actual payload, slay.

πŸ’– DESCRIPTION πŸ’–

okay so this function writes data to Shadow RAM at offset using the EEWR register. that's the core move. πŸ’…

🚨 important warning, bestie: if e1000_update_nvm_checksum is not called after this function, the data will not be committed to FLASH and also Shadow RAM will most likely contain an invalid checksum. not cute. do the checksum call.
😭 and if an error code is returned, data and Shadow RAM may be inconsistent β€” buffer partially written. so like, the vibes are off and the buffer is only partway there.

🌈 SEE ALSO 🌈

mwah πŸ’‹ β€” source/version: ./drivers/net/ethernet/intel/igb; date: October 2026. that's the footer, bestie, and we ate. πŸŽ€

πŸ“¦ where this page comes from