ieee80211_ca...rx_timestamp(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ieee80211_calculate_rx_timestamp(9) 💅

okay so this is from the Kernel API Manual, and bestie, it's a little function with a big job: it figures out when a frame actually showed up. timestamp math, but make it fashion. ✨

🌸 NAME 🌸

ieee80211_calculate_rx_timestamp — calculate timestamp in frame. that's it. that's the whole vibe. 🎀

✨ SYNOPSIS ✨

u64 ieee80211_calculate_rx_timestamp (struct ieee80211_hw *hw , struct
ieee80211_rx_status *status , unsigned int mpdu_len , unsigned int
mpdu_offset );

like, look at her. four arguments, one u64 return, zero drama (mostly). 💖

🦋 ARGUMENTS 🦋

  • hw — the pointer you got from ieee80211_alloc_hw. yes, that one. the hardware said hi 👋
  • status — the RX status. the receipts of the reception, if you will 💅
  • mpdu_len — total MPDU length, including FCS. don't forget the FCS, bestie, it counts 😤
  • mpdu_offset — offset into the MPDU where you want the timestamp calculated. pick a spot, any spot 📍

💜 DESCRIPTION 💜

so what she does is: she calculates the RX timestamp at the given MPDU offset, and she takes into account what the RX timestamp was. like she's doing the math around the existing timestamp, not ignoring it. the way that she's aware 🧚

and here's the cute part — an offset of 0 will just normalize the timestamp to TSF at beginning of MPDU reception. zero? she snaps it right back to the start of the reception. iconic behavior, honestly 👑

🌈 RETURN 🌈

the calculated timestamp. that's the whole return. one u64, fully calculated, no notes. 🔥

⭐ SEE ALSO ⭐

kay so. this list is long long. like, group-chat-with-200-members long. but every single one of these is a real reference and you're gonna get all of them, because I don't gatekeep 💖

and that's the whole page, bestie 🫶 shoutout to ./include/net, dated October 2026, living in the Kernel API Manual — timestamp math never looked so cute. go normalize that TSF, you've got this 💅💖🎀

📦 where this page comes from