phylink_eth...settings_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie so this is a page from the Kernel API Manual and it's genuinely not scary, i promise 🫢 it's just one little function that reads your link settings for you. let's go ✨


🌸 NAME 🌸

phylink_ethtool_ksettings_get β€” get the current link settings


πŸŽ€ SYNOPSIS πŸŽ€

int phylink_ethtool_ksettings_get (struct phylink *pl , struct
       ethtool_link_ksettings *kset );

like, that's it. that's the whole signature. iconic πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • pl β€” a pointer to a struct phylink returned from phylink_create. yes, that phylink_create β€” you gotta get it from there, no cap, don't be out here making your own πŸ“
  • kset β€” a pointer to a struct ethtool_link_ksettings to hold link settings. this is the lil container where the settings get dropped off. it's giving "bring your own bucket" energy πŸ™ˆ

⭐ DESCRIPTION ⭐

Read the current link settings for the phylink instance specified by pl. πŸ“–

and here's the part that's lowkey important β€” the settings you get back are the link settings read from the MAC, PHY or fixed link settings, depending on the current negotiation mode. so like, where it pulls from is literally decided by whatever negotiation mode is active atm. highkey it's just "trust the function, it knows where to look" 🧚


πŸ”₯ SEE ALSO πŸ”₯

the whole phylink friend group showed up, and honestly? they ate πŸ‘‘

Kernel file ./drivers/net/phy/phylink.c

ngl that's a long list but every single one of them is a real one, go read them, i'll wait πŸ’–

bye bestie!! this page lives in <code>./drivers/net/phy</code>, it's dated <b>October 2026</b>, and yeah β€” that header up top said phylink_eth...settings_get(9) but the real full name is phylink_ethtool_ksettings_get. slay πŸ’œβœ¨πŸŽ€

πŸ“¦ where this page comes from