ENUM IWL_RX_PHY_FLAGS(9)
π 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
- 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