__igb_access_emi_reg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __igb_access_emi_reg β€” Kernel API Manual, bestie edition πŸŽ€

okay so real talk: the manual name on this one is literally Kernel API Manual, and the function we're obsessing over today is __igb_access_emi_reg. she's a little EMI register go-between and she ate. let's get into it ✨


🌸 NAME 🌸

__igb_access_emi_reg β€” Read/write EMI register

like. that's the whole vibe. you read it, you write it, you're iconic πŸ’–


✨ SYNOPSIS ✨

s32 __igb_access_emi_reg (struct e1000_hw *hw , u16 address , u16 *data
, bool read );

she returns an s32, no cap. 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

so here's the group chat roll call β€” every single one of these matters, don't skip:

  • hw β€” pointer to the HW structure. that's your hardware bff, she holds everything.
  • address β€” the EMI address to program. you're telling her where to go πŸ’…
  • data β€” pointer to the value to read/write from/to the EMI address. note the pointer energy, she doesn't hold the value herself, she points at it. main character behavior fr fr.
  • read β€” a boolean flag to indicate read or write. true? reading. otherwise? writing. she's flexible like that πŸ”₯
⚠️ lowkey important: data is a pointer and read picks the direction. get those two confused and nothing slays. 😭

πŸ‘‘ SEE ALSO πŸ‘‘

bestie the whole 82575/82580/i350 fam shows up here, plus the actual kernel file they live in. no gatekeeping, all links:

Kernel file ./drivers/net/ethernet/intel/igb/e1000_82575.c

like, that's the whole friend group πŸ’€ every last one of them. iykyk 🌈


okay that's the page!! 🧚 this cutie lives over at ./drivers/net/ethernet/intel/igb, and the version tag says October 2026 β€” so bestie is from the future, slay β­πŸ’œ

πŸ“¦ where this page comes from