EX(4)

πŸ“¦
version 11.0 Β· 2 versions
, in nixpkgs unstable

okay so this is EX(4) from the Kernel Interfaces Manual, and she's literally the page for ex, the driver for 3Com Fast EtherLink XL (3c900, 3c905, 3c980) and similar PCI bus and cardbus Ethernet interfaces. no cap. 🫢

✨ NAME ✨

ex is the driver for 3Com Fast EtherLink XL (3c900, 3c905, 3c980) and similar PCI bus and cardbus Ethernet interfaces. that's the whole vibe. πŸ’…

πŸ¦‹ SYNOPSIS πŸ¦‹

ex* at cardbus? function ?
ex* at pci? dev ? function ?

🌸 DESCRIPTION 🌸

3Com Ethernet and Fast Ethernet cards supported by the ex driver include these legends:

  • 3c450-TX β€” 10/100 Ethernet
  • 3c555 β€” MiniPCI 10/100 Ethernet
  • 3c575-TX β€” Ethernet
  • 3c575B-TX β€” Ethernet
  • 3c575CT β€” Ethernet
  • 3c656 β€” MiniPCI 10/100 Ethernet
  • 3c656B β€” MiniPCI 10/100 Ethernet
  • 3c656C β€” MiniPCI 10/100 Ethernet
  • 3c900-TPO β€” Ethernet
  • 3c900-COMBO β€” Ethernet
  • 3c900B-TPC β€” Ethernet
  • 3c900B-TPO β€” Ethernet
  • 3c900B-COMBO β€” Ethernet
  • 3c905-T4 β€” 10/100 Ethernet
  • 3c905-TX β€” 10/100 Ethernet
  • 3c905B-COMBO β€” 10/100 Ethernet
  • 3c905B-FX β€” 10/100 Ethernet
  • 3c905B-T4 β€” 10/100 Ethernet
  • 3c905B-TX β€” 10/100 Ethernet
  • 3c905CX-TX β€” 10/100 Ethernet
  • 3c980 β€” Server Adapter 10/100 Ethernet
  • 3c980C-TXM β€” 10/100 Ethernet
  • 3cSOHO100-TX β€” 10/100 Ethernet

okay and here's the tea: all versions of the EtherLink XL β€” except the older 3c900 and 3c905 β€” support IPv4/TCP/UDP checksumming in hardware. the ex driver supports this feature of the chip. see ifconfig(8) for information on how to enable this feature. slay. πŸ”₯

🧚 MEDIA SELECTION 🧚

some of these network interfaces support the Media Independent Interface (MII), a bus which can have at least one arbitrary Physical interface (PHY) chip on it. NetBSD supports MII and has separate drivers for many different PHY chips, including ukphy(4), a generic PHY driver that can support many PHY chips that NetBSD does not yet have a specific driver for. iconic. πŸ’œ

support for the PHY found on a given NIC must be configured into a NetBSD kernel config(1) for this driver to work properly in those cases.

see ifmedia(4), and mii(4).

πŸ’€ DIAGNOSTICS πŸ’€

these are the diagnostic strings, verbatim β€” recognize and respect them, bestie:

%s: adapter failure (%x)
%s: can't allocate download descriptors, error = %d
%s: can't allocate or map rx buffers
%s: can't allocate upload descriptors, error = %d
%s: can't create download desc. DMA map, error = %d
%s: can't create rx DMA map %d, error = %d
%s: can't create tx DMA map %d, error = %d
%s: can't create upload desc. DMA map, error = %d
%s: can't load download desc. DMA map, error = %d
%s: can't load mbuf chain, error = %d
%s: can't load rx buffer, error = %d
%s: can't load upload desc. DMA map, error = %d
%s: can't map download descriptors, error = %d
%s: can't map upload descriptors, error = %d
%s: fifo underrun (%x) @%d
%s: jabber (%x)
%s: receive stalled
%s: too many segments,
%s: uplistptr was 0  host too slow to serve incoming packets

🌈 SEE ALSO 🌈

go read these too, iykyk:

πŸŽ€ that's the whole page, bestie β€” from Debian, dated October 30, 2007, and it's the EX(4) manual. mwah πŸ’‹

πŸ“¦ where this page comes from