qed_get_fw_...lts_buf_size(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… qed_get_fw_asserts_results_buf_size(9) β€” like, the Kernel API Manual edition ✨

okay so bestie, welcome to the Kernel API Manual section of the kernel docs πŸŽ€ β€” this one's about qed_get_fw_asserts_results_buf_size, which ngl sounds like a keyboard smash but it's literally just a "how big does my buffer need to be" helper. Let's get into it 🫢


✨ NAME ✨

qed_get_fw_asserts_results_buf_size β€” returns the required buffer size for FW Asserts results, in bytes. that's it, that's the whole job πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

enum dbg_status qed_get_fw_asserts_results_buf_size (struct qed_hwfn
*p_hwfn , u32 *dump_buf , u32 num_dumped_dwords , u32 *results_buf_size
);

returns an enum dbg_status, periodt πŸ’…


🌸 ARGUMENTS 🌸

  • p_hwfn β€” HW device data. the main character struct, the hardware's whole vibe check πŸ–₯️✨
  • dump_buf β€” FW Asserts dump buffer. this is where the dumped stuff lives πŸ“¦
  • num_dumped_dwords β€” number of dwords that were dumped. girl math but with dwords, iykyk πŸ”’
  • results_buf_size β€” (OUT) required buffer size (in bytes) for the parsed results. note the (OUT) β€” this one gets filled in by the function, she's the output queen πŸ‘‘πŸ’–

πŸ”₯ RETURN πŸ”₯

error if the parsing fails, ok otherwise. no in-between, it's giving binary energy fr fr πŸ’€βœ…


πŸ‘‘ SEE ALSO πŸ‘‘

so many friends, honestly iconic of her to link the whole squad 🌈:


that's the whole page bestie, you ate reading all of that πŸ“πŸ’œ this little love letter ships from ./drivers/net/ethernet/qlogic/qed, dated October 2026, and yes that's the same qed_get_fw_...lts_buf_size(9) energy you came in with 🧚✨ mwah, bye! πŸŽ€

πŸ“¦ where this page comes from