qed_mcp_get_board_config(9)
β¨ qed_mcp_get_board_config(9) β¨
okay so bestie, we're in the Kernel API Manual today and this one is literally a little getter in the qed driver β it's giving "just tell me the board config please" π
πΈ NAME πΈ
qed_mcp_get_board_config β get board configuration. that's it, that's the whole vibe π
π¦ SYNOPSIS π¦
int qed_mcp_get_board_config (struct qed_hwfn *p_hwfn , struct qed_ptt
* p_ptt , u32 *p_board_config );
like, three args in, one int out, no cap β¨
π ARGUMENTS π
p_hwfnβ the HW device data. the main character struct fr π«Άp_pttβP_ptt. yes bestie, that's genuinely all it says, i'm not gatekeeping anything from you πp_board_configβ the board config. this is where the answer lands, so keep your eyes on it π
π₯ RETURN π₯
it returns an Int, and here's the tea:
0β operation was successful. slay, we ate π-EBUSYβ operation failed. busy little error, not the moment, try again later π
π SEE ALSO π
first up, the kernel file itself: ./drivers/net/ethernet/qlogic/qed/qed_mcp.h β go read it, iykyk π
and now the whole friend group, literally everyone this function hangs out with:
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_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_get_resc_info(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)
and that's the whole page bestie, go get that board config π§π
π one last cute sign-off: this little masterpiece lives in ./drivers/net/ethernet/qlogic/qed, and it's dated October 2026 β so yeah, it's from the future, we stay 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