phy_port_update_supported(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… phy_port_update_supported(9) πŸ’…

okay bestie, welcome to the Kernel API Manual entry for phy_port_update_supported β€” yes the header says phy_port_update_supported(9) twice, that's just how manpages do, we don't question it πŸŽ€


✨ NAME ✨

phy_port_update_supported β€” sets up the port->supported field 🫢


🌸 SYNOPSIS 🌸

void phy_port_update_supported (struct phy_port *port );

literally that's the whole thing. no return value, no drama, no cap πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • port β€” the port you're updating, bestie. that's the one. the port in question πŸ‘‘

πŸ’– DESCRIPTION πŸ’–

so here's the vibe check: once the port's medium list and number of pairs have already been configured β€” based on firmware, straps, and vendor-specific properties β€” then you may call this function to update the port's supported linkmodes list. ✨

and the icon behaviour, the moment everybody needs to know: any mode that was manually set in the port's supported list remains set. πŸŽ€ like, it stays. it's a main character, it's not getting dropped. periodt. πŸ’€

ngl this is one of those "call it at exactly the right time or don't call it" situations β€” the medium list and pair count gotta be locked in first, iykyk 😭

🧚 SEE ALSO 🧚

like a little friend group of functions fr fr 🌈


that's the whole page, bestie β€” no more, no less πŸ“

signing off from ./drivers/net/phy, dated October 2026 β€” catch you in the next phy_port_update_supported(9) footer, mwah πŸ’œ

πŸ“¦ where this page comes from