mucse_fw_send_cmd_wait_resp(9)
π mucse_fw_send_cmd_wait_resp β like, the Kernel API Manual page you didn't know you needed π
okay bestie, so this one lives in the Kernel API Manual and it's literally the little messenger girl of the mucse driver β she carries your command over to the firmware and then waits for the reply like a loyal bestie holding your iced coffee. no cap. π
β¨ NAME β¨
mucse_fw_send_cmd_wait_resp β send cmd req and wait for response π
π¦ SYNOPSIS π¦
int mucse_fw_send_cmd_wait_resp (struct mucse_hw *hw , union
mbx_fw_cmd_req_u *req , union mbx_fw_cmd_reply_u *reply );
πΈ ARGUMENTS πΈ
hwβ pointer to the HW structure. the main character's home base, if you will πreqβ pointer to the cmd req structure. the message she's delivering fr fr πreplyβ pointer to the fw reply structure. where the answer gets dropped off π«Ά
π DESCRIPTION π
okay so mucse_fw_send_cmd_wait_resp sends req to the pf-fw mailbox and then waits for the reply from fw. that's it, that's the whole vibe. she's a synchronous queen β no running off before the answer comes back, periodt. β³β¨
π₯ RETURN π₯
0 on success, negative errno on failure. so if you get a negative back, that's your sign to look at it with concern ππ
π SEE ALSO π
- Kernel file
./drivers/net/ethernet/mucse/rnpgbe/rnpgbe_mbx_fw.cβ the source, go read it iykyk π mucse_mbx_get_info(9)mucse_mbx_sync_fw(9)mucse_mbx_powerup(9)mucse_mbx_reset_hw(9)mucse_mbx_get_macaddr(9)
the whole friend group omg π«Άπ
ngl this is a synchronous mailbox call β it sends and then waits, so don't act surprised when it blocks, bestie π§
and that's the page!! sign-off time: this lil beauty comes from ./drivers/net/ethernet/mucse/r... and it's dated October 2026, so she's future-iconic πβπ
π¦ 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