ice_aq_list_caps(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, this is ice_aq_list_caps(9) from the Kernel API Manual, and it’s giving β€œask firmware what capabilities it has” energy πŸ’…βœ¨ no cap, we’re keeping every detail.

πŸ’– NAME πŸ’–

ice_aq_list_caps β€” query function/device capabilities πŸŽ€

✨ SYNOPSIS ✨

the signature is literally:

int ice_aq_list_caps (struct ice_hw *hw , void *buf , u16 buf_size , u32
       *cap_count , enum ice_adminq_opc opc , struct ice_sq_cd *cd );

πŸŽ€ ARGUMENTS πŸŽ€

okay so the little cast of characters:

  • hw β€” pointer to the HW struct.
  • buf β€” a buffer to hold the capabilities.
  • buf_size β€” size of the buffer.
  • cap_count β€” if not NULL, set to the number of capabilities reported.
  • opc β€” capabilities type to discover, device or function.
  • cd β€” pointer to command details structure or NULL.

πŸ¦‹ DESCRIPTION πŸ¦‹

Get the function (0x000A) or device (0x000B) capabilities description from firmware and store it in the buffer. periodt.

If the cap_count pointer is not NULL, then it is set to the number of capabilities firmware will report. count check slay ✨

⚠️ heads up bestie: if the buffer size is too small, it is possible the command will return ICE_AQ_ERR_ENOMEM. The cap_count will still be updated in this case. It is recommended that the buffer size be set to ICE_AQ_MAX_BUF_LEN (the largest possible buffer that firmware could return) to avoid this.

🌈 SEE ALSO 🌈

the whole ice squad is here, iykyk:

okay bye bestie! 🫢 signed off from ./drivers/net/ethernet/intel/ice, dated October 2026, on the ice_aq_list_caps(9) page β€” mwah πŸ’‹

πŸ“¦ where this page comes from