brcmf_p2p_add_vif(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– brcmf_p2p_add_vif β€” the Kernel API Manual tea πŸ«–

okay so bestie, welcome to brcmf_p2p_add_vif(9) from the Kernel API Manual β€” yes, the Kernel API Manual, we're in the big leagues now ✨ this is the page that tells you how to spin up a brand-new P2P virtual interface, and honestly? it's giving "let there be wifi" energy 🌈


πŸ’… NAME

brcmf_p2p_add_vif β€” create a new P2P virtual interface. that's it. that's the whole vibe. one job, does it iconically πŸ‘‘


πŸŽ€ SYNOPSIS

struct wireless_dev * brcmf_p2p_add_vif (struct wiphy *wiphy , const
char *name , unsigned char name_assign_type , enum nl80211_iftype type ,
struct vif_params *params );

look at that signature. five args, returns a struct wireless_dev *. main character function fr fr πŸ’…


✨ ARGUMENTS

okay so here's who's who in the group chat:

  • wiphy β€” the wiphy device of the new interface. like, the parent energy. this is where your shiny new iface is getting born 🍼
  • name β€” the name of the new interface. its government name, if you will πŸŽ€
  • name_assign_type β€” the origin of the interface name. where the name came from. its lore, basically πŸ“œ
  • type β€” the nl80211 interface type. so it knows what kind of iface it's supposed to be πŸ¦‹
  • params β€” contains the mac address for the P2P device. yes, the mac address lives in here. no cap πŸ’–

🌸 SEE ALSO

buckle up bestie, this list is LONG and every single one of these is invited to the party πŸŽ‰ no skipping, no cutting, we are thorough in this house:

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


ngl that's a lot of cross-references but that's just how the brcmfmac p2p family rolls β€” they're all interconnected, iykyk πŸ’€

and that's the page bestie!! 🧚 source is ./drivers/net/wireless/broadco... and this gorgeous little doc is dated October 2026 β€” so jot that down, stay hydrated, and go create some P2P virtual interfaces πŸ’œπŸŒΈ

πŸ“¦ where this page comes from