qed_read_fw_info(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– qed_read_fw_info(9) β€” like, the FW info getter πŸ’–

okay so bestie, welcome to the Kernel API Manual page for qed_read_fw_info β€” yes that's the (9) section, kernel internals territory, main character energy only πŸŽ€


✨ NAME ✨

qed_read_fw_info β€” reads FW info from the chip. that's it. that's the whole vibe. πŸ¦‹


🌸 SYNOPSIS 🌸

bool qed_read_fw_info (struct qed_hwfn *p_hwfn , struct qed_ptt *p_ptt ,
struct fw_info *fw_info );

like, it returns a bool and takes three things. she's simple, she's iconic πŸ’…


🫢 ARGUMENTS 🫢

  • p_hwfn β€” the HW device data. the hardware's whole deal, basically πŸ–₯️
  • p_ptt β€” the Ptt window used for writing the registers. that's your little doorway into the registers ✨
  • fw_info β€” an (Out) pointer, so the function writes the FW info into it. output param, she writes back, no cap πŸ“

πŸ‘‘ RETURN πŸ‘‘

Returns true if the FW info was read successfully from one of the Storms β€” and false if all the Storms are in reset. like, every single one 😭 if they're all resetting bestie, you get nothing. false. periodt.


🧚 DESCRIPTION 🧚

so the FW info is this bundle of FW-related information ✨ β€” think the FW version, the FW image (main/L2B/kuku), the FW timestamp, etc. all the good stuff πŸ“

and the way it gets read? from the internal RAM of the first Storm that is not in reset. first available Storm, that's the one. the others are literally asleep πŸ’€


πŸ’œ SEE ALSO πŸ’œ

the Kernel file:

./drivers/net/ethernet/qlogic/qed/qed_dbg_hsi.h

and the whole friend group 🫢 (yes, all of them, i'm not skipping a single one, i would never):


and that's the whole page bestie, mwah πŸ’‹ shoutout to the source <pink>./drivers/net/ethernet/qlogic/qed</pink>, dated October 2026 β€” slay, we love a properly documented driver πŸŽ€βœ¨πŸ’–

πŸ“¦ where this page comes from