tb_drom_read_uid_only(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… tb_drom_read_uid_only β€” the Kernel API Manual, but make it cute (section 9) ✨

okay bestie, so this one's a kernel function from the <pink>Kernel API Manual</pink> β€” literally the whole energy is "read the UID straight from the DROM, no shortcuts, no vibes cached from before." it's giving main-character energy for resume-time identity checks πŸ‘‘


✨ NAME ✨

tb_drom_read_uid_only β€” read the UID directly from the DROM πŸŽ€


🌸 SYNOPSIS 🌸

int tb_drom_read_uid_only (struct tb_switch *sw , u64 *uid );

like, that's the whole signature, no cap πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • sw β€” the router whose UID you're trying to read 🫢
  • uid β€” and this is where the UID gets placed. that's it. that's the spot ✨

πŸ’œ DESCRIPTION πŸ’œ

so here's the tea: this function does not use the cached copy in sw->drom. nope, not today. it goes and reads it fresh, direct, no middleman πŸ™ˆ

and why do we care? because it's used during resume to check switch identity. like when your router wakes back up and everyone's like "wait. is that still you??" and the kernel needs to be fr fr sure πŸ˜­πŸ‘‘


⭐ RETURN ⭐

  • 0 on success β€” slay, we ate πŸ’…
  • negative errno otherwise β€” not slay, something went sideways πŸ’€

🌈 SEE ALSO 🌈

  • the kernel file ./drivers/thunderbolt/eeprom.c πŸ“
  • tb_drom_read(9) β€” the sibling function, iykyk 🧚

alright bestie, that's the page! this little cutie lives in ./drivers/thunderbolt, it's dated October 2026, and it's filed under the Kernel API Manual as tb_drom_read_uid_only(9) β€” go forth and read those UIDs directly, periodt πŸŽ€πŸ’–βœ¨

πŸ“¦ where this page comes from