wl1271_cmd_interrogate(9)

📦 version 7.3.1, in nixpkgs unstable

💖 wl1271_cmd_interrogate(9) 💖

okay so welcome to the Kernel API Manual bestie, we're literally about to read an acx out of the firmware and it's gonna be cute 🎀

✨ NAME ✨

wl1271_cmd_interrogate — read acx from firmware 🦋

like, that's the whole vibe. you interrogate the firmware. the firmware gives you an acx. slay.

🌸 SYNOPSIS 🌸

int wl1271_cmd_interrogate (struct wl1271 *wl , u16 id , void *buf ,
       size_t cmd_len , size_t res_len );

five arguments, no cap. we're gonna go through every single one 💅

👑 ARGUMENTS 👑

  • wl — the wl struct. that's it, that's the whole description, she's mysterious like that 🙈
  • id — the acx id. which acx are we interrogating? this one. periodt 🔥
  • buf — buffer for the response, including all headers, and it must work with dma. not me stressing the dma part, but fr fr, dma-compatible or it's not it 💀
  • cmd_len — length of command. the command. its length. iconic 🌈
  • res_len — length of payload. yes, that's a different length than cmd_len, don't get it twisted bestie 🫶

🔍 SEE ALSO 🔍

kernel file ./drivers/net/wireless/ti/wlcore/cmd.c — go read her, she has the lore 📖

both of these are also giving main character energy, highly recommend ✨

lowkey reminder that buf has to include all the headers and has to play nice with dma — that's not a suggestion, that's the vibe check 🧚

and that's the page bestie!! 💜 brought to you by the source at ./drivers/net/wireless/ti/wlcore, dated October 2026, and yeah the footer had the title on it too but we already covered that up top 😭 mwah, study hard, drink water, don't dma on unaligned buffers 🍓💖

📦 where this page comes from