STRUCT RTL8365MB_EXTINT(9)
π struct rtl8365mb_extint(9) β external interface info π¦
okay bestie so this is a page from the Kernel API Manual and it's about struct rtl8365mb_extint, which is literally just a tiny little struct that keeps track of where a port's external interface is at. it's giving "small but essential" energy, no cap π
β¨ SYNOPSIS β¨
struct rtl8365mb_extint {
int port;
int id;
unsigned int supported_interfaces;
};
that's the whole thing. three members. tiny icon, huge role π
πΈ Members πΈ
portβ the port that's got an external interface hanging off it. like, which port, bestie.idβ the external interface ID π«Ά and heads up, this one's picky: it's either0,1, or2. those are the only valid values, periodt.supported_interfacesβ a bitmask of the supported PHY interface modes β¨ yes, a bitmask, so it's one of those "read the bits" situations, iykyk.
π Description π
so basically this struct represents a mapping, and the mapping is:
port -> { id, supported_interfaces }
that's it, that's the vibe π it's meant to be embedded in struct rtl8365mb_chip_info for every port that has an external interface. so like, one of these little guys per external-interface port, all cozied up inside the chip info struct π
π₯ SEE ALSO π₯
- Kernel file
./drivers/net/dsa/realtek/rtl8365mb_main.c enum rtl8365mb_vlan_egress_mode(9)struct rtl8365mb_chip_info(9)struct rtl8365mb_cpu(9)struct rtl8365mb_port(9)struct rtl8365mb(9)
okay that's the whole page bestie, go read the neighbors too, they're all in the same friend group π§π
this masterpiece lives in ./drivers/net/dsa/realtek, and it's dated October 2026 β so yes, the docs are time-traveling, and honestly? slay β mwah π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms