fw_run_transaction(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fw_run_transaction(9) β€” Kernel API Manual πŸ’…

okay so bestie, this is the Kernel API Manual page for fw_run_transaction(9), and it's giving β€œsend a request, then sleep until the transaction is completed” main character energy. no cap. πŸ¦‹


✨ NAME ✨

fw_run_transaction β€” send request and sleep until transaction is completed πŸ’€


πŸŽ€ SYNOPSIS πŸŽ€

int fw_run_transaction (struct fw_card *card , int tcode , int destination_id , int generation , int speed , unsigned long long offset , void *payload , size_t length );

🌸 ARGUMENTS 🌸

  • card β€” the card interface for this request 🫢
  • tcode β€” the transaction code ✨
  • destination_id β€” the destination node ID, consisting of bus_ID and phy_ID 🎯
  • generation β€” the bus generation in which the request and response are valid πŸŒ€
  • speed β€” the transmission speed ⚑
  • offset β€” a 48bit wide offset into the destination's address space πŸ“
  • payload β€” the data payload for the request subaction πŸ“¦
  • length β€” the length of the payload, in bytes πŸ“

πŸ’– DESCRIPTION πŸ’–

It returns the RCODE. See fw_send_request for parameter documentation. πŸ‘€

Unlike fw_send_request, data points to the payload of the request or/and to the payload of the response. πŸ”

⚠️ DMA mapping restrictions apply to outbound request payloads of >= 8 bytes but not to inbound response payloads. So like… clock that tea, bestie. 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/firewire/core-transaction.c:


xoxo bestie πŸ’– β€” source/version: ./drivers/firewire, date: October 2026, page: fw_run_transaction(9). it's literally iconic. slay and goodbye. ✨

πŸ“¦ where this page comes from