STRUCT MV88E6XXX_DEVLINK_VTU_ENTRY(9)
π NAME π
okay bestie, welcome to the Kernel API Manual page for struct mv88e...nk_vtu_entry(9) β the NAME line says struct mv88e6xxx_devlink_vtu_entry and it's the Devlink VTU entry. That's the title tea, periodt. π
β¨ SYNOPSIS β¨
struct mv88e6xxx_devlink_vtu_entry {
u16 fid;
u16 sid;
u16 op;
u16 vid;
u16 data[3];
u16 resvd;
};
π«Ά Members π«Ά
fidβGlobal1/2: FID and VLAN policy.sidβGlobal1/3: SID, unknown filters and learning.opβGlobal1/5: FID (old chipsets).vidβGlobal1/6: VID, valid, and page.dataβGlobal1/7-9: Membership data and priority override.resvdβ Reserved. Also happens to align the size to16B.
π Description π
okay so the VTU entry format varies between chipset generations β the descriptions above represent the superset of all possible information, and not all fields are valid on all devices. Since this is a low-level debug interface, copy all data verbatim and defer parsing to the consumer. That's the whole assignment, bestie. π«Ά
π SEE ALSO π
- Kernel file
./drivers/net/dsa/mv88e6xxx/devlink.c struct mv88e6xxx_devlink_stu_entry(9)
xoxo π signing off from ./drivers/net/dsa/mv88e6xxx, dated October 2026, still repping struct mv88e...nk_vtu_entry(9) β slay your debugging, bestie β¨π
π¦ 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