__genphy_config_aneg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ __genphy_config_aneg(9) ✨

okay so bestie, welcome to the Kernel API Manual β€” yes that's the whole manual name, we're in the big-leagues section 9 now πŸ’… and today's main character is __genphy_config_aneg. she's lowkey the one who decides whether your ethernet phy renegotiates its whole vibe with the link partner, or just gets a BMCR written at it. no cap, she's iconic.


🌸 NAME 🌸

__genphy_config_aneg β€” restart auto-negotiation or write BMCR 🫢

like. that's literally her job description and she does it flawlessly.


πŸ¦‹ SYNOPSIS πŸ¦‹

int __genphy_config_aneg (struct phy_device *phydev , bool changed );

that's the whole signature, copy it exactly, don't @ me πŸ™ˆ


πŸŽ€ ARGUMENTS πŸŽ€

  • phydev β€” the target phy_device struct πŸ’– this is the phy we're doing all of this for, she's the main character of the struct world
  • changed β€” a bool, and it tells us whether autoneg is requested πŸ‘‘ iykyk

⭐ DESCRIPTION ⭐

okay so here's the tea, and it's genuinely simple:

  • if auto-negotiation is enabled, we configure the advertising, and then we restart auto-negotiation ✨
  • if it is not enabled, then we write the BMCR 🌈

that's it. that's the whole function. two paths, both slay, zero notes. periodt. πŸ’…


πŸ”₯ SEE ALSO πŸ”₯

this list is LONG bestie, do not skip it, every single one of these got invited to the group chat 🎊

Kernel file ./drivers/net/phy/phy_device.c β€” and then, alphabetically-ish, the whole squad:


ngl the SEE ALSO list is giving "everyone showed up to the function's birthday party" and honestly? we love that for her πŸ§šπŸ“

and that's the whole page, bestie πŸ’œ sourced straight from ./drivers/net/phy, dated October 2026, and yes β€” __genphy_config_aneg(9) is still her name, she never changed it, she never will. mwah πŸŽ€πŸŒΈβœ¨

πŸ“¦ where this page comes from