STRUCT IWL_TRANS_INFO(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ struct iwl_trans_info(9) ✨

okay bestie, welcome to the Kernel API Manual β€” yes, we're doing kernel pages now, and honestly? this one's a cutie. it's the little struct that carries all the transport info the outside world is allowed to peek at. 🫢


🌸 NAME 🌸

struct iwl_trans_info β€” transport info for outside use. that's it. that's the whole vibe. it's the "here's what you're allowed to know" bag of goodies. πŸ’…


✨ SYNOPSIS ✨

struct iwl_trans_info {
    const char *name;
    u32 max_skb_frags;
    u32 hw_rev;
    u32 hw_rev_step;
    u32 hw_rf_id;
    u32 hw_crf_id;
    u32 hw_cnv_id;
    u32 hw_id;
    u8 pcie_link_speed;
    u8 num_rxqs;
 };

look at her. ten fields, not one of them wasted. iconic. πŸ‘‘


πŸŽ€ Members πŸŽ€

  • name β€” the device name. literally just what the device calls itself, no cap. 🏷️
  • max_skb_frags β€” the maximum number of fragments an SKB can have when it's transmitted. and here's the tea: 0 means frag SKBs (NETIF_F_SG) aren't supported at all β€” so zero is not a "no limit" situation, it's a "we don't do that here" situation. remember that. πŸ’€
  • hw_rev β€” the revision data of the HW. the hardware's whole resumΓ©, basically.
  • hw_rev_step β€” The mac step of the HW. (yes, capital T, capital mac step, it's giving official.) 🌟
  • hw_rf_id β€” the device RF ID. πŸ¦‹
  • hw_crf_id β€” the device CRF ID.
  • hw_cnv_id β€” the device CNV ID. (three IDs in a row, she's thorough, we love a thorough queen.)
  • hw_id β€” the ID of the device / sub-device. and the bit math matters, so listen up bestie: Bits 0:15 represent the sub-device ID, and Bits 16:31 represent the device ID. two IDs, one field, she's efficient. 🧚
  • pcie_link_speed β€” current PCIe link speed (PCI_EXP_LNKSTA_CLS_*). ⚠️ only valid for discrete (not integrated) NICs β€” so if you're on an integrated one, this value is not your story, don't @ her.
  • num_rxqs β€” number of RX queues allocated by the transport. count 'em. πŸ”₯

πŸ” SEE ALSO πŸ”

  • Kernel file ./drivers/net/wireless/intel/iwlwifi/iwl-trans.h
  • Transport layer - what is it ?(9)
  • Life cycle of the transport layer(9)
  • enum CMD_MODE(9)
  • struct iwl_device_cmd(9)
  • struct iwl_device_tx_cmd(9)
  • enum iwl_hcmd_dataflag(9)
  • struct iwl_host_cmd(9)
  • enum iwl_trans_status(9)
  • struct iwl_dump_sanitize_ops(9)
  • struct iwl_trans_config(9)
  • struct iwl_trans_rxq_dma_data(9)
  • struct iwl_pnvm_image(9)
  • enum iwl_trans_state(9)
  • Platform power management(9)
  • enum iwl_ini_cfg_state(9)
  • struct iwl_dram_data(9)
  • struct iwl_dram_regions(9)
  • struct iwl_fw_mon(9)
  • struct iwl_self_init_dram(9)
  • struct iwl_imr_data(9)
  • struct iwl_pc_data(9)
  • struct iwl_trans_debug(9)
  • struct iwl_trans(9)
  • iwl_trans_resched_with_nic_access(9)

that's a whole friend group right there, go read them all, iykyk. πŸ’œ


ngl this page is short but she ate. no filler, all facts, and the facts are load-bearing. πŸ“

and that's a wrap, bestie! πŸ’– this lil masterpiece came from ./drivers/net/wireless/intel/i... and it's dated October 2026 β€” go forth and transport responsibly. 🌈⭐

πŸ“¦ where this page comes from