igb_get_pcs_...duplex_82575(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

igb_get_pcs_speed_and_duplex_82575 β€” bestie, this one grabs the current speed and duplex for you ✨

Okay so real quick, before we dive in: this whole page lives in the Kernel API Manual, which is giving very much "the docs that ship with the kernel" energy πŸŽ€ and we're about to get into the PCS of it all.


🌸 SYNOPSIS 🌸

s32 igb_get_pcs_speed_and_duplex_82575 (struct e1000_hw *hw , u16 *speed
, u16 *duplex );

That's the whole vibe right there πŸ’–


πŸ¦‹ ARGUMENTS πŸ¦‹

  • hw β€” pointer to the HW structure πŸ‘‘ that's your hardware context, the main character of this whole operation.
  • speed β€” stores the current speed πŸ“ˆ like, it writes the speed back through this pointer, no cap.
  • duplex β€” stores the current duplex πŸ” same deal, the duplex value gets dropped in here.

✨ DESCRIPTION ✨

Okay so here's the tea β˜• β€” using the physical coding sub-layer (PCS), this function retrieves the current speed and duplex, then stores those values in the pointers you provided 🫢

That's it. That's the function. Lowkey iconic in its simplicity honestly πŸ’… It doesn't set anything, it doesn't configure anything, it just goes and asks the PCS what's up and reports back through speed and duplex. A little messenger. A lil scout. Very demure 🌸


🌈 SEE ALSO 🌈

Buckle up bestie, this list is LONG and we are NOT skipping any of it 😭 every single one, fr fr:

Like I said. LONG. But we ate and left no crumbs πŸ“


Heads up bestie πŸ’– β€” this page is from the kernel's own API docs (Kernel API Manual), and the whole thing lives under ./drivers/net/ethernet/intel/igb. The docs are dated October 2026, so like… future vibes πŸ¦‹

That's the whole thing! Go forth and go get that speed and duplex, queen πŸ‘‘βœ¨

πŸ“¦ where this page comes from