tdme_settxpower(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… tdme_settxpower β€” the kernel API manual, but make it make sense

okay so bestie, welcome to tdme_settxpower(9) from the Kernel API Manual ✨ this is the little function that sets your tx power for MLME_SET phyTransmitPower, and honestly? she's small but she matters πŸŽ€


✨ SYNOPSIS ✨

u8 tdme_settxpower (u8 txp , void *device_ref );

that's it. that's the whole vibe check. two args, one u8 coming back at you 🫢


🌸 ARGUMENTS 🌸

  • txp β€” the Transmit Power. yes, that's the whole description. she's a u8 and she's booked and busy πŸ’…
  • device_ref β€” a "nondescript pointer to target device". not mysterious, not fancy, just a pointer that points at the device you're targeting. no cap πŸ”₯

πŸ’– DESCRIPTION πŸ’–

okay so the actual tea β˜•: the value gets normalised to the 802.15.4 Definition, and that definition is 6-bit, signed. here's the bit map, memorise it bestie:

  • Bit 7-6: not used β€” literally just sitting there, unemployed, iconic of them honestly πŸ™ˆ
  • Bit 5-0: tx power, and the range is -32 - +31 dB 🌈

so like, if you're packing your own bits in there, mind the layout. six bits, signed, that's the moment. periodt. πŸ‘‘


⭐ RETURN ⭐

returns the 802.15.4 status code of api calls β€” so you get a status code back, go check it, don't just ignore it, i'm begging 😭


πŸ¦‹ SEE ALSO πŸ¦‹

the whole friend group, honestly. every single one of them. it's giving group chat with 60 members and everyone's typing 🫢


ngl bestie, this one's short, but "short" β‰  "skip it". the bit layout is the whole point of the page β€” if you mess up bit 7-6 vs bit 5-0 you're gonna have a bad time 😭 πŸ’€

🌈 and that's the page!! sourced from ./drivers/net/ieee802154, Kernel API Manual, dated October 2026 β€” mwah, go set some tx power, you absolute main character πŸ‘‘πŸ’–βœ¨

πŸ“¦ where this page comes from