ENUM BRCMF_NETIF_STOP_REASON(9)
π enum brcmf_netif_stop_reason β like, the whole vibe check
okay so this is a page from the Kernel API Manual (yes bestie, the Kernel API Manual, we're in the big leagues now π) and it's all about one little enum that answers the question every netif queue eventually asks itself: why did you stop? πβ¨
β¨ NAME β¨
enum brcmf_netif_stop_reason β the reason for stopping the netif queue. that's it, that's the whole thing, it's giving very "short and iconic" π
πΈ SYNOPSIS πΈ
enum brcmf_netif_stop_reason {
BRCMF_NETIF_STOP_REASON_FWS_FC ,
BRCMF_NETIF_STOP_REASON_FLOW ,
BRCMF_NETIF_STOP_REASON_DISCONNECTED
};
look at her. three constants, zero drama, fully slaying π and yes, the comma before the closing brace stays exactly where it is, don't come for me π«Ά
π¦ Constants π¦
BRCMF_NETIF_STOP_REASON_FWS_FCβ netif got stopped because of firmware signalling flow control. fw said "chill for a sec" and netif listened, we love a good listener honestly πBRCMF_NETIF_STOP_REASON_FLOWβ netif got stopped because the flowring is full. no room, no cap, queue is at capacity, it's giving "sold out" energy πBRCMF_NETIF_STOP_REASON_DISCONNECTEDβ netif got stopped because it's simply not connected (STA mode). not connected = not sending, that's just the rules bestie π
π SEE ALSO π
go touch some grass and also read these, they're all connected iykyk:
- Kernel file
./drivers/net/wireless/broadcom/brcm80211/brcmfmac/core.hπ struct brcmf_ampdu_rx_reorder(9)struct brcmf_if(9)
fr fr: this is a kernel API page, so if you're here you're lowkey doing real driver work. proud of you. π₯Ήπ
and that's the whole page, mwah π sign-off time: this cutie came out of ./drivers/net/wireless/broadco..., dated October 2026, and it's filed under enum brcmf_n..._stop_reason(9) β periodt. πβ
π¦ 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