ENUM IWL_RX_PHY_FLAGS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

ok so enum iwl_rx_phy_flags β€” it's the enum you use to parse the phy_flags field inside %iwl_rx_phy_info 🫢 that's literally the whole job, bestie.

(this is the enum iwl_rx_phy_flags(9) page from the Kernel API Manual, if u were wondering ✨)


πŸ¦‹ SYNOPSIS πŸ¦‹

here's the whole squad, exactly as they're declared, no cap:

enum iwl_rx_phy_flags {
    RX_RES_PHY_FLAGS_BAND_24 ,
    RX_RES_PHY_FLAGS_MOD_CCK ,
    RX_RES_PHY_FLAGS_SHORT_PREAMBLE ,
    RX_RES_PHY_FLAGS_NARROW_BAND ,
    RX_RES_PHY_FLAGS_ANTENNA ,
    RX_RES_PHY_FLAGS_ANTENNA_POS ,
    RX_RES_PHY_FLAGS_AGG ,
    RX_RES_PHY_FLAGS_OFDM_HT ,
    RX_RES_PHY_FLAGS_OFDM_GF ,
    RX_RES_PHY_FLAGS_OFDM_VHT

};

πŸ‘‘ Constants πŸ‘‘

okay, member-by-member breakdown, and every single one gets its moment πŸ’–

  • RX_RES_PHY_FLAGS_BAND_24 β€” true if the packet was received on 2.4 band 🌸 like, the lil 2.4GHz band. that's the vibe check.
  • RX_RES_PHY_FLAGS_MOD_CCK β€” modulation is CCK. that's what it means, that's what it does πŸ’…
  • RX_RES_PHY_FLAGS_SHORT_PREAMBLE β€” true if packet's preamble was short. short king preamble πŸ‘‘
  • RX_RES_PHY_FLAGS_NARROW_BAND β€” narrow band (<20 MHz) receive. tiny bandwidth, big energy ✨
  • RX_RES_PHY_FLAGS_ANTENNA β€” antenna on which the packet was received. which antenna ate? πŸ“‘
  • RX_RES_PHY_FLAGS_ANTENNA_POS β€” antenna bit position. it's giving where in the bits, iykyk πŸŽ€
  • RX_RES_PHY_FLAGS_AGG β€” set if the packet was part of an A-MPDU. group chat packet fr fr 🫢
  • RX_RES_PHY_FLAGS_OFDM_HT β€” The frame was an HT frame. HT frame main character energy πŸ”₯
  • RX_RES_PHY_FLAGS_OFDM_GF β€” The frame used GF preamble. (GF preamble, iconic behavior honestly) 🌈
  • RX_RES_PHY_FLAGS_OFDM_VHT β€” The frame was a VHT frame. very high throughput, very high slay πŸ’€βœ¨

🧚 SEE ALSO 🧚

go read these next, they're all in the same lore universe ✨ and the kernel file they live in is ./drivers/net/wireless/intel/iwlwifi/fw/api/rx.h β€” like the whole friend group is there:

  • struct iwl_rx_phy_info(9)
  • struct iwl_rx_mpdu_res_start(9)
  • enum iwl_mvm_rx_status(9)
  • struct iwl_rx_mpdu_desc_v1(9)
  • struct iwl_rx_mpdu_desc_v3(9)
  • struct iwl_rx_mpdu_desc(9)
  • struct iwl_rx_no_data(9)
  • struct iwl_rx_no_data_ver_3(9)
  • enum iwl_bar_frame_release_sta_tid(9)
  • enum iwl_bar_frame_release_ba_info(9)
  • struct iwl_bar_frame_release(9)
  • struct iwl_rss_config_cmd(9)
  • struct iwl_rxq_sync_cmd(9)
  • struct iwl_rxq_sync_notification(9)
  • enum iwl_mvm_pm_event(9)
  • struct iwl_mvm_pm_state_notification(9)
  • struct iwl_ba_window_status_notif(9)
  • struct iwl_rfh_queue_data(9)
  • struct iwl_rfh_queue_config(9)
  • struct iwl_beacon_filter_notif_v1(9)
  • struct iwl_beacon_filter_notif(9)
  • struct iwl_rx_phy_air_sniffer_ntfy(9)
ok that's a lot of cross-references but that's the assignment and we don't skip, bestie. every single one matters 🫢

aand that's the page!! 🌟 source/version line says ./drivers/net/wireless/intel/i... and the date stamp is October 2026, so like, mark ur calendar bestie, this one's dated October 2026 πŸ’œ byeeee πŸ’…πŸŽ€

πŸ“¦ where this page comes from