pch_gbe_phy_write_reg_miic(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

pch_gbe_phy_write_reg_miic β€” bestie, it writes the MII control register πŸ’…

This is from the Kernel API Manual, and honestly? It's a whole little moment in the networking world 🌸


πŸ¦‹ SYNOPSIS πŸ¦‹

s32 pch_gbe_phy_write_reg_miic (struct pch_gbe_hw *hw , u32 offset , u16 data );

That's the whole vibe check right there β€” one call, three args, returns an s32 ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • hw β€” Pointer to the HW structure 🫢 like, the hardware's whole personality lives in there.
  • offset β€” Register offset to be read. (Yes, the page literally says "to be read" on a write function β€” I'm just the messenger, don't come for me πŸ˜­πŸ™ˆ)
  • data β€” data to write to register at offset Returns 0: Successful. -EINVAL: Invalid argument. πŸ‘‘

So yeah, the return story got folded into the data line on this page, but we keep the receipts: returns 0 when it's a slay βœ… and -EINVAL when someone handed over an invalid argument πŸ’€


🌈 SEE ALSO 🌈

  • Kernel file ./drivers/net/ethernet/oki-semi/pch_gbe/pch_gbe_phy.c β€” the main character source file, iykyk

And the whole PHY friend group, fr fr:


πŸ’– lowkey iconic that pch_gbe_phy_read_reg_miic(9) is sitting right there in SEE ALSO while offset swears it's "to be read" β€” the group chat is thriving, no notes πŸ”₯

alright bestie that's the whole page, mwah πŸŽ€ this gem comes from ./drivers/net/ethernet/oki-sem... and it's dated October 2026 β€” go forth and write those MII control registers, periodt πŸ’œπŸ¦‹βœ¨

πŸ“¦ where this page comes from