bnx2x_mcast...store_cmd_e1(9)

✨ NAME ✨

Okay so this is bnx2x_mcast_handle_restore_cmd_e1 — the restore command handler, but specifically for the 57710 chip 💅 welcome bestie, it's a lil one 🎀

---

🌸 SYNOPSIS 🌸

int bnx2x_mcast_handle_restore_cmd_e1 (struct bnx2x *bp , struct
       bnx2x_mcast_obj *o , int start_idx , int *rdata_idx );

---

🦋 ARGUMENTS 🦋

• bp — the device handle, aka your main character pointer 🫶
• o — the multicast info, all the mcast vibes live here ✨
• start_idx — the index in the registry you're starting from 🏁
• rdata_idx — the index in the ramrod data you're starting from 🚀

---

👑 DESCRIPTION 👑

So the restore command for 57710 is exactly like all the other commands bestie — it's always a stand alone command 💀 which means start_idx and rdata_idx will always, and I mean always, be 0. No cap. 🎯

This function will always succeed ✨ like it's literally that girl, it cannot fail 😭

Oh and — plot twist 🙈 — it returns -1 to comply with the 57712 variant. Yeah. It succeeds and returns -1. Slay, I guess 💅 that's just how the family does it.

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/net/ethernet/broadcom/bnx2x/bnx2x_sp.c 🍓

The whole friend group, in order, no skipping 🫶:

• bnx2x_exe_queue_init(9), bnx2x_exe_queue_add(9), bnx2x_exe_queue_step(9), bnx2x_state_wait(9), __bnx2x_vlan_mac_h_write_trylock(9), __bnx2x_vlan_mac_h_exec_pending(9), __bnx2x_vlan_mac_h_pend(9), __bnx2x_vlan_mac_h_write_unlock(9), __bnx2x_vlan_mac_h_read_lock(9), bnx2x_vlan_mac_h_read_lock(9), __bnx2x_vlan_mac_h_read_unlock(9), bnx2x_vlan_mac_h_read_unlock(9), bnx2x_vlan_mac_set_cmd_hdr_e2(9), bnx2x_vlan_mac_set_rdata_hdr_e2(9), bnx2x_vlan_mac_set_rdata_hdr_e1x(9), bnx2x_set_one_mac_e1x(9), bnx2x_set_one_vlan_mac_e1h(9), bnx2x_vlan_mac_restore(9), bnx2x_validate_vlan_mac_add(9), bnx2x_validate_vlan_mac_del(9), bnx2x_validate_vlan_mac_move(9), bnx2x_wait_vlan_mac(9), bnx2x_complete_vlan_mac(9), bnx2x_optimize_vlan_mac(9), bnx2x_vlan_mac_get_registry_elem(9), bnx2x_execute_vlan_mac(9), bnx2x_config_vlan_mac(9), bnx2x_vlan_mac_del_all(9), bnx2x_mcast_get_next_bin(9), bnx2x_mcast_clear_first_bin(9), bnx2x_mcast_handle_restore_cmd_e2(9), bnx2x_mcast_handle_current_cmd(9), bnx2x_mcast_set_rdata_hdr_e2(9), bnx2x_mcast_refresh_registry_e2(9), bnx2x_mcast_set_rdata_hdr_e1(9), bnx2x_get_fw_mac_addr(9), bnx2x_mcast_refresh_registry_e1(9), __atomic_add_ifless(9), __atomic_dec_ifmoe(9), bnx2x_init_credit_pool(9), bnx2x_debug_print_ind_table(9), bnx2x_setup_rss(9), bnx2x_queue_state_change(9), bnx2x_queue_comp_cmd(9), bnx2x_q_init(9), bnx2x_q_send_deactivate(9), bnx2x_q_send_activate(9), bnx2x_queue_chk_transition(9), bnx2x_func_state_change_comp(9), bnx2x_func_comp_cmd(9), bnx2x_func_chk_transition(9), bnx2x_func_init_func(9), bnx2x_func_init_port(9), bnx2x_func_init_cmn_chip(9), bnx2x_func_init_cmn(9), bnx2x_func_reset_func(9), bnx2x_func_reset_port(9), bnx2x_func_reset_cmn(9), bnx2x_func_state_change(9)

---

ngl bestie the whole page was basically "it does nothing, it can't fail, it returns -1 anyway" and honestly? iconic behavior. 💀👑

Byeee 🫶 this lil page lives at ./drivers/net/ethernet/broadco... (yes it's cut off, that's just how it is 💅), it's dated October 2026, and it goes by bnx2x_mcast...store_cmd_e1(9) in the Kernel API Manual — go read it again, it's short, you got this 🎀✨