qed_mcp_get_...sceiver_data(9)
π qed_mcp_get_transceiver_data β fresh off the Kernel API Manual π
okay bestie, welcome to qed_mcp_get_...sceiver_data(9) β yes the header truncates it like that, she's got main character energy and a limited character budget, we respect it. this is the Kernel API Manual page for qed_mcp_get_transceiver_data, and it does exactly one thing: it gets the transceiver data of the port. that's it. that's the vibe. β¨
β¨ NAME β¨
qed_mcp_get_transceiver_data β Get transceiver data of the port. no cap, that's literally the whole job.
πΈ SYNOPSIS πΈ
int qed_mcp_get_transceiver_data (struct qed_hwfn *p_hwfn , struct
qed_ptt *p_ptt , u32 *p_transceiver_state , u32 *p_tranceiver_type );
she takes four args and gives you back an int. it's giving "small function, big responsibilities" π«Ά
π¦ ARGUMENTS π¦
p_hwfnβ HW device data. the hardware's whole little identity, handed over. iconic.p_pttβ P_ptt. that's it, that's the description. the manual said "P_ptt" and then clocked out π we love a low-effort queen.p_transceiver_stateβ Transceiver state. this is where the state of the transceiver lands.p_tranceiver_typeβ Media type value. and yes, it is spelledp_tranceiver_typeright there in the manual β do not come for her spelling, she's been through enough π copy it exactly as written or your compile will simply not slay.
π RETURN π
returns an int, and here's the whole tea:
0β operation was a success. (the page says "Operation was successul" and honestly? iconic. we're keeping her exactly as she is π)-EBUSYβ operation failed. busy little error, showing up to ruin the party π
π SEE ALSO π
the kernel file herself lives at:
./drivers/net/ethernet/qlogic/qed/qed_mcp.h
and she rolls deep with her friend group, so here's the entire squad, no one left out, fr fr:
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_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_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)
like I said: the whole group chat π«Ά
ngl bestie, if the return is-EBUSY, the operation failed β don't go reading your transceiver state and pretending everything's fine. check theint, always. π
and that's the page!! brought to you by the ./drivers/net/ethernet/qlogic/qed crew, dated October 2026 β mwah, periodt, go read your qed_mcp.h ππΈ
π¦ 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