STRUCT QUEUE_ENTRY_PRIV_USB_BCN(9)

💖 struct queue_entry_priv_usb_bcn — the Kernel API Manual glow-up 💖

okay so bestie, welcome to the manual page for struct queue_entry_priv_usb_bcn(9) — yes that whole entire name, say it with your chest. this is section 9 of the Kernel API Manual, and it's basically the little sidecar of USB-specific info that rides along with every single TX queue entry. she's small, she's specific, she's lowkey iconic. 🎀

---

✨ NAME ✨

struct queue_entry_priv_usb_bcn — the per-TX-entry USB-specific information. that's it, that's her whole job. ngl it's giving "supporting character with main character energy." 💅

---

🦋 SYNOPSIS 🦋

here's the whole vibe, verbatim, no cap:

struct queue_entry_priv_usb_bcn {
    struct urb *urb;
    unsigned int guardian_data;
    struct urb *guardian_urb;
 };

like, three members, zero drama. she ate and left no crumbs. ✨

---

🌸 Members 🌸

• urb — the Urb structure used for device communication. this is the actual messenger doing the talking to the device, fr fr. 🫶
• guardian_data — set to 0, and it's used for sending the guardian data. yes bestie, she ships the guardian data. that's the whole assignment. 💜
• guardian_urb — the Urb structure used to send the guardian data. so it's the dedicated little courier for exactly that guardian errand. 🧚

---

🌈 Description 🌈

okay so here's the important part: the first section should match struct queue_entry_priv_usb exactly. like, exactly exactly. don't get creative, don't freestyle, don't try to put your own spin on it — that is a matching situation and we respect it. 👑

and then rt2500usb can use this structure to send a guardian byte when working with beacons. that's the special occasion where this whole struct gets to shine — beacons, guardian byte, whole thing. periodt. 🔥

---

👑 SEE ALSO 👑

the whole squad, no one left behind. first up, the kernel file itself:

./drivers/net/wireless/ralink/rt2x00/rt2x00usb.h

and now the guest list 💀:

• enum rt2x00usb_vendor_request(9)
• enum rt2x00usb_mode_offset(9)
• rt2x00usb_vendor_request(9)
• rt2x00usb_vendor_request_buff(9)
• rt2x00usb_vendor_request_sw(9)
• rt2x00usb_eeprom_read(9)
• rt2x00usb_register_read(9)
• rt2x00usb_register_read_lock(9)
• rt2x00usb_register_multiread(9)
• rt2x00usb_register_write(9)
• rt2x00usb_register_write_lock(9)
• rt2x00usb_register_multiwrite(9)
• rt2x00usb_regbusy_read(9)
• rt2x00usb_register_read_async(9)
• struct queue_entry_priv_usb(9)
• rt2x00usb_kick_queue(9)
• rt2x00usb_flush_queue(9)
• rt2x00usb_watchdog(9)

(the way rt2x00usb_vendor_request(9) shows up twice in the original list — yeah she's just like that, double-booked and thriving. 💀 not me pointing it out, but also not me deleting it. we keep it.) 🍓

---

bestie reminder: if you're editing this struct, keep that first section matching struct queue_entry_priv_usb exactly. that's not a vibe suggestion, that's the whole description. 🙈

---

and that's the page!! 🎀 sourced from ./drivers/net/wireless/ralink/..., dated October 2026, filed under struct queu...priv_usb_bcn(9). mwah, go read the other rt2x00usb pages, ily, bye!! 💖🦋✨