brcmf_p2p_ge...ent_chanspec(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… brcmf_p2p_get_current_chanspec β€” a Kernel API Manual moment (section 9, bestie)

okay so picture this: you're deep in the Kernel API Manual, section 9, and the page you opened is literally titled brcmf_p2p_ge...ent_chanspec(9) (yes the header truncates it like that, we don't make the rules). The whole thing is about one little function and honestly? she's short, she's sweet, she gets the job done. let's go πŸŽ€


✨ NAME ✨

brcmf_p2p_get_current_chanspec β€” Get current operation channel. that's it. that's the whole vibe. πŸ’–


🌸 SYNOPSIS 🌸

void brcmf_p2p_get_current_chanspec (struct brcmf_p2p_info *p2p , u16
*chanspec );

no cap, that's the entire signature. void return, two args, slay. ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • p2p β€” P2P specific data. (she's the struct, she's the moment β€” struct brcmf_p2p_info *)
  • chanspec β€” chanspec to be returned. (yes babes, it's an output situation β€” a u16 * where the answer lands 🫢)

πŸ‘‘ SEE ALSO πŸ‘‘

okay this part is a lot and I'm obsessed with it. first the file:

  • Kernel file ./drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c

and then the whole extended friend group, in exactly the order the page lists them:

like, that's the whole group chat right there. πŸ’€πŸ’–

lowkey reminder bestie: these are all section 9 kernel entries, so if you're reading them off the top of your head you're doing it wrong β€” go look them up fr fr. πŸ™ˆ

anyway that's the page!! tiny function, huge friend list, iconic energy. go get your chanspec and live your truth ✨

catch you later β€” this one's from ./drivers/net/wireless/broadco..., dated October 2026, and the manual name on the tin is brcmf_p2p_ge...ent_chanspec(9) πŸŽ€ mwah πŸ’‹

πŸ“¦ where this page comes from