VTE(4)

✨ VTE(4) ✨

okay so like, this is the FreeBSD Kernel Interfaces Manual for the vte driver, and it's genuinely iconic for all the Vortex86 girlies out there 💅

---

💖 NAME 💖

vte — the Vortex86 RDC R6040 Fast Ethernet driver, no cap.

✨ SYNOPSIS ✨

bestie, if you wanna compile this driver into the kernel, you literally just put these lines in your kernel configuration file:

device miibus
device vte

or, lowkey alternatively, to load the driver as a module at boot time, you drop this line in loader.conf(5):

if_vte_load="YES"

🦋 DESCRIPTION 🦋

so the vte device driver provides support for the RDC R6040 Fast Ethernet controller — which is commonly found on Vortex86 System On a Chip (SoC). main character energy fr fr.

the RDC R6040 has an integrated 10/100 PHY for 10/100Mbps support in full or half-duplex. The controller supports interrupt moderation mechanism, a 64-bit multicast hash filter, VLAN over-size frame and four station addresses. The vte device driver uses three station addresses out of four as perfect multicast filter.

the vte driver supports the following media types:

• autoselect — Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to rc.conf(5). slay.
• 10baseT/UTP — Set 10Mbps operation.
• 100baseTX — Set 100Mbps (Fast Ethernet) operation.

and it also supports these media options:

• full-duplex — Force full duplex operation.
• half-duplex — Force half duplex operation.

for more info on configuring this device, see ifconfig(8). iykyk.

🌸 HARDWARE 🌸

the vte device driver provides support for the following Ethernet controllers:

• DM&P Vortex86 RDC R6040 Fast Ethernet controller

🎀 LOADER TUNABLES 🎀

tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5). periodt.

• hw.vte.tx_deep_copy — okay so here's the tea: the RDC R6040 controller has no auto-padding support for short frames and the controller's DMA engine does not have capability to handle multiple buffers for a TX frame such that driver has to create a single contiguous TX buffer. This hardware limitation leads to poor TX performance since most of CPU cycles are wasted on both de-fragmenting mbuf chains and padding. This tunable enables deep copy operation for TX frames such that driver will spend less CPU cycles in de-fragmentation with the cost of extra TX buffer memory. The default value is 1 to use deep copy. 💅

💜 SYSCTL VARIABLES 💜

the following variables are available as both sysctl(8) variables and loader(8) tunables:

• dev.vte.%d.rx_mod — Maximum number of packets to fire RX completion interrupt. The accepted range is 0 to 15, the default is 15.
• dev.vte.%d.tx_mod — Maximum number of packets to fire TX completion interrupt. The accepted range is 0 to 15, the default is 15.
• dev.vte.%d.stats — Show hardware MAC statistics maintained in driver.

🌈 SEE ALSO 🌈

altq(4), arp(4), miibus(4), netintro(4), ng_ether(4), vlan(4), ifconfig(8)

DM&P Electronics Inc. Vortex86, http://www.dmp.com.tw.

👑 HISTORY 👑

the vte driver was written by Pyun YongHyeon <yongari@FreeBSD.org>. It first appeared in FreeBSD 8.3.

---

this page is from Debian, dated December 30, 2010, and it's for VTE(4) — bye bestie, hope this helped! 🫶✨