phy_caps_me...et_supported(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– phy_caps_medium_get_supported β€” NAME ✨

okay so bestie, this is a page from the Kernel API Manual, and the function we're stanning today is phy_caps_medium_get_supported β€” literally "returns linkmodes supported on a given medium" πŸŽ€ that's the whole vibe, she tells you which linkmodes your medium can do.


🌸 SYNOPSIS 🌸

void phy_caps_medium_get_supported (unsigned long *supported , enum
ethtool_link_medium medium , int pairs );

that's it, that's the whole call. no return value, she just fills your buffer and dips πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • supported β€” the output param, the main character of this whole operation ✨ after the call, this holds all possible linkmodes on the given medium, and with the given number of pairs, or less. like, she's generous, she'll give you the under-pairs options too 🫢
  • medium β€” the medium you want the support info from. this is the "who are we asking about" of it all πŸ’œ
  • pairs β€” how many pairs are used on that given medium. lowkey important note: this only matters for modes that even support this notion, like BaseT. if it's not applicable to what you're doing, just pass 0 and move on πŸ™ˆ

⭐ DESCRIPTION ⭐

okay so here's the one (1) behaviour detail you cannot miss: if no match exists, the supported field is left untouched. like, she doesn't clear it, she doesn't zero it, she doesn't touch it, periodt πŸ’€ so whatever was in there before? still there. plan accordingly bestie 😭


πŸŽ€ SEE ALSO πŸŽ€

the kernel file is ./drivers/net/phy/phy_caps.c β€” that's the source of truth, iykyk πŸ‘‘

and the whole phy_caps friend group, all iconic, all worth a read:


🌈 okay that's the page!! this one lives over at ./drivers/net/phy, dated October 2026, from the Kernel API Manual β€” go forth and get those supported linkmodes, bestie, you got this πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from