STRUCT BRCMF_BUS_MSGBUF(9)
π struct brcmf_bus_msgbuf(9) β Kernel API Manual β¨
okay so bestie, lemme introduce you to struct brcmf_bus_msgbuf β lowkey the bus ringbuf go-to "if" when we're in the msgbuf case. it's giving infrastructure, it's giving main character energy for the wireless stack π¦.
β¨ SYNOPSIS β¨
struct brcmf_bus_msgbuf {
struct brcmf_commonring *commonrings[BRCMF_NROF_COMMON_MSGRINGS];
struct brcmf_commonring **flowrings;
u32 rx_dataoffset;
u32 max_rxbufpost;
u16 max_flowrings;
u16 max_submissionrings;
u16 max_completionrings;
};
π Members π
commonringsβ the commonrings that are always there, no cap. they're the ride-or-dies π.flowringsβ commonrings that get dynamically created and destroyed for data π. they come and go, honestly iconic.rx_dataoffsetβ if this is set, then all rx data has this offset, periodt.max_rxbufpostβ the absolute max number of buffers you can post for rx π₯. it's giving capacity queen.max_flowringsβ the maximum number of tx flow rings supported π.max_submissionringsβ the maximum number of submission rings (h2d) supported π«.max_completionringsβ the maximum number of completion rings (d2h) supported πΈ.
π SEE ALSO π
go look at the kernel file, it's literally right here bestie:
./drivers/net/wireless/broadcom/brcm80211/brcmfmac/bus.h
and while you're at it, say hi to the fam π«Ά:
struct brcmf_bus_ops(9)struct brcmf_bus_stats(9)struct brcmf_bus(9)
k that's the whole vibe, fr fr. this page is comin' at you straight from ./drivers/net/wireless/broadco... β October 2026 edition, struct brcmf_bus_msgbuf(9) and all π. slay, go forth and read your structs π§ββοΈβ¨.
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms