qed_mcp_get_resc_info(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’« qed_mcp_get_resc_info β€” a Kernel API Manual moment πŸ’«

okay so bestie, welcome to qed_mcp_get_resc_info(9) from the Kernel API Manual, like literally the whole page is about one function and honestly? she's serving. this is the little guy that Gets the MFW allocation info for the given resource, no cap πŸŽ€


✨ SYNOPSIS ✨

int qed_mcp_get_resc_info (struct qed_hwfn *p_hwfn , struct qed_ptt
*p_ptt , enum qed_resources res_id , u32 *p_mcp_resp , u32 *p_resc_num ,
u32 *p_resc_start );

that's the whole signature, copy it exactly bestie, don't @ me πŸ’…


🌸 ARGUMENTS 🌸

  • p_hwfn β€” HW device data. the hardware's whole vibe and identity 🫢
  • p_ptt β€” P_ptt. yes queen, that's the description, that's all we got, iconic brevity πŸ’€
  • res_id β€” Res ID. which resource we're talking about ✨
  • p_mcp_resp β€” MCP resp. the MCP's response lands here πŸ“¬
  • p_resc_num β€” Resc num. the number of rescs, dropping right here πŸ”₯
  • p_resc_start β€” Resc start. and this one's for where the rescs start, periodt πŸ‘‘

πŸ’– RETURN πŸ’–

Int β€” and the value is 0 β€” meaning the operation was successful. slay. that's it, that's the return πŸ’€βœ¨

heads up bestie, the page does say 0 = success and genuinely does not tell us anything else about other return values. do not make up lore that isn't there πŸ™ˆ

πŸ¦‹ SEE ALSO πŸ¦‹

first up, the kernel file itself: ./drivers/net/ethernet/qlogic/qed/qed_mcp.h β€” go read her, she knows things πŸ“–

and then… the entire friend group, like the biggest group chat in the kernel, all of them (9), all present and accounted for:

qed_mcp_get_link_params(9), qed_mcp_get_link_state(9), qed_mcp_get_link_capabilities(9), qed_mcp_set_link(9), qed_mcp_get_mfw_ver(9), qed_mcp_get_mbi_ver(9), qed_mcp_get_media_type(9), qed_mcp_get_transceiver_data(9), qed_mcp_trans_speed_mask(9), qed_mcp_get_board_config(9), qed_mcp_cmd(9), qed_mcp_cmd_nosleep(9), qed_mcp_drain(9), qed_mcp_get_flash_size(9), qed_mcp_send_drv_version(9), qed_get_process_kill_counter(9), qed_start_recovery_process(9), qed_recovery_prolog(9), qed_mcp_ov_update_current_config(9), qed_mcp_ov_update_driver_state(9), qed_mcp_ov_update_mtu(9), qed_mcp_ov_update_mac(9), qed_mcp_ov_update_wol(9), qed_mcp_set_led(9), qed_mcp_nvm_read(9), qed_mcp_nvm_write(9), qed_mcp_nvm_resp(9), qed_mcp_get_nvm_image_att(9), qed_mcp_get_nvm_image(9), qed_mcp_bist_register_test(9), qed_mcp_bist_clock_test(9), qed_mcp_bist_nvm_get_num_images(9), qed_mcp_bist_nvm_get_image_att(9), qed_mfw_process_tlv_req(9), qed_mcp_send_raw_debug_data(9), qed_mcp_is_ext_speed_supported(9), qed_mcp_cmd_init(9), qed_mcp_cmd_port_init(9), qed_mcp_free(9), qed_mcp_handle_events(9), qed_mcp_load_req(9), qed_mcp_load_done(9), qed_mcp_unload_req(9), qed_mcp_unload_done(9), qed_mcp_read_mb(9), qed_mcp_ack_vf_flr(9), qed_mcp_fill_shmem_func_info(9), qed_mcp_reset(9), qed_mcp_nvm_rd_cmd(9), qed_mcp_phy_sfp_read(9), qed_mcp_is_init(9), qed_mcp_config_vf_msix(9), qed_mcp_halt(9), qed_mcp_resume(9), qed_mcp_set_resc_max_val(9), qed_mcp_ov_update_eswitch(9), qed_mcp_initiate_pf_flr(9), qed_mcp_resc_lock(9), qed_mcp_resc_unlock(9), qed_mcp_resc_lock_default_init(9), qed_mcp_is_smart_an_supported(9), qed_mcp_get_capabilities(9), qed_mcp_set_capabilities(9), qed_mcp_read_ufp_config(9), qed_mcp_nvm_info_populate(9), qed_mcp_nvm_info_free(9), qed_mcp_get_engine_config(9), qed_mcp_get_ppfid_bitmap(9), qed_mcp_nvm_get_cfg(9), qed_mcp_nvm_set_cfg(9), qed_mcp_is_esl_supported(9), qed_mcp_get_esl_status(9)

like, that's the whole roster. iykyk πŸ’œ


and that's the page, bestie πŸŒˆπŸ’– this one lives at ./drivers/net/ethernet/qlogic/qed, dated October 2026, and it's literally qed_mcp_get_resc_info(9) the whole way down. mwah πŸ’…πŸŽ€

πŸ“¦ where this page comes from