wiphy_to_ieee80211_hw(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– wiphy_to_ieee80211_hw(9) πŸ’–

okay bestie, welcome to the Kernel API Manual page for wiphy_to_ieee80211_hw(9) β€” yes the title is also the vibe, we move. This is the little lookup that turns a wiphy into the mac80211 driver's hw struct, and it's lowkey iconic.

πŸŽ€ NAME πŸŽ€

wiphy_to_ieee80211_hw β€” return a mac80211 driver hw struct from a wiphy. That's the whole assignment, fr fr.

✨ SYNOPSIS ✨

struct ieee80211_hw * wiphy_to_ieee80211_hw (struct wiphy *wiphy );

Copy it exactly, bestie β€” no autocorrect energy.

🌸 ARGUMENTS 🌸

  • wiphy β€” the struct wiphy which we want to query. That's the one you're handing over.

πŸ’… DESCRIPTION πŸ’…

okay so mac80211 drivers can use this to get to their respective struct ieee80211_hw. Once a driver has that, and it wants its own private structure, it can then access it via hw->priv.

The one note that matters: mac802111 drivers should not use wiphy_priv to try to get their private driver structure, because that thing is already used internally by mac80211. Do not fight the internals, bestie, they will win. πŸ’€

πŸ¦‹ RETURN πŸ¦‹

The mac80211 driver hw struct of wiphy. That's it, that's the gift. 🎁

🌈 SEE ALSO 🌈

Kernel file: ./include/net/mac80211.h β€” and then the entire extended universe, no cap. All of these are exactly the references from the page:


and that's the page, bestie. source/version vibe: ./include/net; date on the footer: October 2026; footer title: wiphy_to_ieee80211_hw(9). bye bestie, go get that hw struct πŸ’…βœ¨

πŸ“¦ where this page comes from