e1000_power..._80003es2lan(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… e1000_power_down_phy_copper_80003es2lan β€” Kernel API Manual, section (9)

okay bestie, sit down, because we're about to get INTIMATE with a kernel function whose name is genuinely a whole paragraph. This one lives in the Kernel API Manual, section 9, and she's a networking girlie through and through. πŸ¦‹


✨ NAME ✨

e1000_power_down_phy_copper_80003es2lan β€” literally just "Remove link during PHY power down." That's the whole vibe. She pulls the link when the PHY is going night-night. 😴


🌸 SYNOPSIS 🌸

void e1000_power_down_phy_copper_80003es2lan (struct e1000_hw *hw );

Returns nothing (void β€” she gives, she doesn't take πŸ’…), takes exactly one thing, and yes the function name is that long, no we are not okay about it.


πŸŽ€ ARGUMENTS πŸŽ€

  • hw β€” pointer to the HW structure 🫢 that's it. that's the whole argument list. one (1) pointer. the HW structure. love that for her.

πŸ”₯ DESCRIPTION πŸ”₯

So here's the situation, bestie. There are a few scenarios where we're powering down the PHY to save power, and in all of them we gotta remove the link. The list, because lists are iconic:

  • when the PHY is powered down to save power ⚑
  • when we need to turn off the link during a driver unload πŸ“€
  • when wake on lan is not enabled 🚫

In those cases: remove the link. That's the job. She does it. No cap. πŸ‘‘


🌈 SEE ALSO 🌈

okay this is the part where the whole friend group shows up β€” like, the entire 80003es2lan family reunion, plus where to find the source. no one gets left out, periodt:

like… she really said "you will know my entire extended family." respect. 🫑


and that's the page, bestie ✨ sourced from ./drivers/net/ethernet/intel/e..., dated October 2026, and filed under e1000_power..._80003es2lan(9) because apparently even the footer wanted to abbreviate that name. 😭 go forth and power down those PHYs responsibly πŸ’œπŸŽ€

πŸ“¦ where this page comes from