e1000e_read_...g_igp_locked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

e1000e_read_phy_reg_igp_locked β€” read igp PHY register ✨

Yup bestie, you're on the e1000e_read_...g_igp_locked(9) page from the Kernel API Manual, and it's giving very specific kernel-function energy πŸ’…

✨ SYNOPSIS ✨

s32 e1000e_read_phy_reg_igp_locked (struct e1000_hw *hw , u32 offset , u16 *data );

πŸŽ€ ARGUMENTS πŸŽ€

  • hw β€” pointer to the HW structure 🫢
  • offset β€” register offset to be read πŸ”
  • data β€” pointer to the read data πŸ“

🌸 DESCRIPTION 🌸

So this function reads the PHY register at offset and stores the retrieved information in data. That's the whole vibe, no cap πŸ’–

Heads up bestie: it assumes the semaphore is already acquired 😭 Like, do not roll up to this function without your semaphore already handled, okay?

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./drivers/net/ethernet/intel/e1000e/phy.c β€” go look, it's iconic πŸ‘‘

And here's the whole linked squad, every single one, no gatekeeping:


Okay that's literally the whole page, bestie 🫢 This lil manual came from ./drivers/net/ethernet/intel/e..., was dated October 2026, and the footer still says e1000e_read_...g_igp_locked(9) β€” periodt πŸ’…βœ¨

πŸ“¦ where this page comes from