ice_capture_crosststamp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 ice_capture_crosststamp(9) 🌸

okay bestie, so this lil page lives in the Kernel API Manual and it's about ice_capture_crosststamp β€” the function that captures a device/system cross timestamp ✨ which sounds fake but it's real and it's iconic.


πŸ’« NAME πŸ’«

ice_capture_crosststamp β€” capture a device/system cross timestamp 🫢


✨ SYNOPSIS ✨

int ice_capture_crosststamp (ktime_t *device , struct
system_counterval_t *system , void *__ctx );

πŸŽ€ ARGUMENTS πŸŽ€

  • device β€” the current device time πŸ’…
  • system β€” the system counter value, read synchronously with the device time. like they're literally read together, main character energy, no cap πŸ¦‹
  • __ctx β€” the context passed from ice_ptp_getcrosststamp 🌸

πŸ”₯ DESCRIPTION πŸ”₯

So what it does: it reads the device clock and the system (ART) clock simultaneously, then returns the corrected clock values in ns. two clocks, one moment, absolutely slaying βœ¨πŸ‘‘


⭐ RETURN ⭐

zero on success, or a negative error code on failure. that's it, that's the vibe check πŸ’€

ngl if you get nonzero back, something went wrong. negative error code = not the moment.

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/net/ethernet/intel/ice/ice_ptp.c β€” and okay buckle up bestie, 'cause the whole family's here 😭

like I said, the whole family 😭🫢


and that's the page!! πŸ’– this one's from ./drivers/net/ethernet/intel/ice, dated October 2026, and it's ice_capture_crosststamp(9) β€” go read the source bestie, it's giving ✨ πŸŽ€πŸ‘‘

πŸ“¦ where this page comes from