ixgbe_out_i2c_byte_ack(9)
π ixgbe_out_i2c_byte_ack(9) π
okay bestie, welcome to the Kernel API Manual, section 9 β yes, the real one, we're literally in the kernel docs right now π this little page is all about one tiny function that pushes a byte out over I2C and waits for the ack. lowkey iconic behavior.
β¨ NAME β¨
ixgbe_out_i2c_byte_ack β Send I2C byte with ack. that's the whole vibe, no notes π«Ά
πΈ SYNOPSIS πΈ
int ixgbe_out_i2c_byte_ack (struct ixgbe_hw *hw , u8 byte );
π¦ ARGUMENTS π¦
hwβ pointer to the hardware structure. yes the big struct, she's the main character here πbyteβ byte to send. one single byte, out it goes π
π DESCRIPTION π
Returns an error code on error. that's it, that's the description π short and sweet, fr fr β so if something goes wrong, you get an error code back, and that's your signal to pay attention. no cap.
π SEE ALSO π
first up, the literal source file, right here in the kernel tree:
./drivers/net/ethernet/intel/ixgbe/ixgbe_phy.c
and now the whole entire friend group β every single one of these cuties, no skipping, i promised:
ixgbe_in_i2c_byte_ack(9)ixgbe_ones_comp_byte_add(9)ixgbe_read_i2c_combined_generic_int(9)ixgbe_write_i2c_combined_generic_int(9)ixgbe_probe_phy(9)ixgbe_identify_phy_generic(9)ixgbe_check_reset_blocked(9)ixgbe_get_phy_id(9)ixgbe_get_phy_type_from_id(9)ixgbe_reset_phy_generic(9)ixgbe_read_phy_reg_mdi(9)ixgbe_read_phy_reg_generic(9)ixgbe_write_phy_reg_mdi(9)ixgbe_write_phy_reg_generic(9)ixgbe_msca_cmd(9)ixgbe_mii_bus_read_generic_c22(9)ixgbe_mii_bus_read_generic_c45(9)ixgbe_mii_bus_write_generic_c22(9)ixgbe_mii_bus_write_generic_c45(9)ixgbe_mii_bus_read_c22(9)ixgbe_mii_bus_read_c45(9)ixgbe_mii_bus_write_c22(9)ixgbe_mii_bus_write_c45(9)ixgbe_x550em_a_mii_bus_read_c22(9)ixgbe_x550em_a_mii_bus_read_c45(9)ixgbe_x550em_a_mii_bus_write_c22(9)ixgbe_x550em_a_mii_bus_write_c45(9)ixgbe_get_first_secondary_devfn(9)ixgbe_x550em_a_has_mii(9)ixgbe_mii_bus_init(9)ixgbe_setup_phy_link_generic(9)ixgbe_setup_phy_link_speed_generic(9)ixgbe_get_copper_speeds_supported(9)ixgbe_get_copper_link_capabilities_generic(9)ixgbe_check_phy_link_tnx(9)ixgbe_setup_phy_link_tnx(9)ixgbe_reset_phy_nl(9)ixgbe_identify_module_generic(9)ixgbe_identify_sfp_module_generic(9)ixgbe_identify_qsfp_module_generic(9)ixgbe_get_sfp_init_sequence_offsets(9)ixgbe_read_i2c_eeprom_generic(9)ixgbe_read_i2c_sff8472_generic(9)ixgbe_write_i2c_eeprom_generic(9)ixgbe_is_sfp_probe(9)ixgbe_read_i2c_byte_generic_int(9)ixgbe_read_i2c_byte_generic(9)ixgbe_read_i2c_byte_generic_unlocked(9)ixgbe_write_i2c_byte_generic_int(9)ixgbe_write_i2c_byte_generic(9)ixgbe_write_i2c_byte_generic_unlocked(9)ixgbe_i2c_start(9)ixgbe_i2c_stop(9)ixgbe_clock_in_i2c_byte(9)ixgbe_clock_out_i2c_byte(9)ixgbe_get_i2c_ack(9)ixgbe_clock_in_i2c_bit(9)ixgbe_clock_out_i2c_bit(9)ixgbe_raise_i2c_clk(9)ixgbe_lower_i2c_clk(9)ixgbe_set_i2c_data(9)ixgbe_get_i2c_data(9)ixgbe_i2c_bus_clear(9)ixgbe_tn_check_overtemp(9)
like. sixty-four of them. she knows everyone at the party πβ¨ respect honestly.
quick reminder bestie: that's the registered sequence β don't go assuming they behave a certain way just because the names are cute. the names are the names, the behaviour lives in the source π«Ά
that's the page!! mwah π source lives at ./drivers/net/ethernet/intel/i... (yes it's abbreviated up there, blame the footer, not me π) and we're stamped October 2026. go forth and ack your bytes, queen ππ
π¦ 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