Search tools, AI agents, MCP servers
Submit a tool

Search iThub

Search tools, categories and collections. Type at least two characters.

Explore all tools
↑ ↓ to explore resultsEnter to open · Esc to close
E

EVDI

Linux kernel module and libevdi library from DisplayLink that add virtual displays managed by user-space programs

Workstations & EndpointsOpen sourcev1.15.1

EVDI at a glance

Pricing
Open source
Deployment
Linux app
License
Open source
Version
v1.15.1September 15, 2026
Platforms
Linux
Language
C
Data location
Runs locally in the Linux kernel and in the client process on the host; screen buffers are allocated and read by the client application.
Maker
DisplayLink
Founded
2015

What is EVDI?

EVDI, the Extensible Virtual Display Interface, is a Linux kernel module that adds virtual displays to a system and lets a user-space program receive the image the system renders on them. The project repository contains three parts: the evdi kernel module, the libevdi wrapper library that applications use to talk to the module, and pyevdi, a Python wrapper for libevdi. The README describes the result as a virtual display that can be added, removed and read for screen updates from an application built on libevdi.

The project is published by DisplayLink (UK) Ltd, now part of Synaptics, with copyright notices from 2015 to 2026. According to the EVDI documentation, DisplayLink started it as the base of its display driver for Ubuntu Linux, which drives USB 3.0 docking stations and USB display adapters, and then published the code because the interface was generic enough for other applications. The same page states that the library API is not yet stable and that clients may need matching updates.

EVDI is usually installed together with the proprietary DisplayLink user mode driver. The README states that EVDI is not a complete driver for DisplayLink devices and that the user mode driver is required for full functionality. DisplayLink ships it as a deb package or inside a standalone installer on the DisplayLink Ubuntu download page. The release notes of DisplayLink USB Graphics Software for Ubuntu 6.4.0, dated September 24, 2026, list EVDI v1.15.1 as the included version. GitHub releases contain source code only; RPM packages for Fedora, CentOS Stream, Rocky Linux and AlmaLinux come from the community displaylink-rpm project, and an evdi-dkms package for Arch Linux is maintained in the AUR by the community.

The latest GitHub release is v1.15.1, published September 15, 2026, which restores the painter pipeline when a reconnect arrives without a modeset. v1.15.0 (July 1, 2026) replaced version and distribution conditionals with build probes, added preliminary support for Linux kernel 7.2 and fixed builds on Enterprise Linux 9.8 and 10.2. Earlier 1.14.x releases added preliminary support for kernels 6.19 and 7.0, fixed artifacts and scanout buffer errors on Intel Meteor Lake and Core Ultra platforms, and changed the libevdi license to LGPL v2.1 or later.

The code is written in C, with C++ and pybind11 for pyevdi. Licensing is split by folder: the kernel module is under GPL v2, the library under LGPL v2.1 or later, and the remaining files under the MIT license unless a folder has its own LICENSE file. The README lists two areas for future work: the communication between the kernel module and libevdi is not access-controlled or authenticated, and the module is a platform_driver because virtual displays cannot be enumerated at the hardware level. Device enumeration and control of DisplayLink hardware are handled by the separate user mode driver, not by EVDI.

Key capabilities

  • evdi kernel module A DRM/KMS driver that registers virtual displays imitating physical monitors and exposes the frame buffer contents the system renders on them. The Kconfig entry DRM_EVDI depends on DRM and USB support and selects the DRM KMS helper. Because it works with the standard Linux DRM subsystem, the README states that its displays can be controlled with standard tools such as xrandr or the display settings of Unity, GNOME or KDE.
  • libevdi C library A shared library (libevdi.so.1, version 1.15.1) that wraps the communication with the kernel module. Applications use it to find or request EVDI nodes, connect a monitor description, register buffers and receive screen updates. It builds against libdrm and uses semantic versioning, where a MAJOR change marks an incompatible API change.
  • pyevdi Python bindings A Python wrapper for libevdi, built with pybind11 through a Makefile in a Python virtual environment. The pyevdi README documents build, installation and a pytest suite. The main README states that virtual displays can also be created with pyevdi.
  • DKMS packaging The module ships a dkms.conf with automatic installation enabled, so DKMS rebuilds it for new kernels, and installs it under /kernel/drivers/gpu/drm/evdi. A dkms_install.sh script adds the module options and the auto-load configuration. The deb package built by the project CI is named evdi and depends on dkms and mokutil.
  • Kernel version range The README gives 4.15 as the minimum kernel version and states that DisplayLink has verified that the module compiles and works with Ubuntu variants of kernels up to 6.15. Other vanilla kernel sources are used in CI jobs, and newer kernels or kernels of other distributions may require extra development. The DisplayLink Ubuntu 6.4.0 release notes state a supported range of 4.15 to 7.3.0-rc3 for the full driver package.
  • Node management EVDI reuses the DRM cardX nodes for messages between kernel and user space. evdi_check_device reports whether a node was created by EVDI, and libevdi refuses to connect to other DRM nodes such as a built-in GPU. Since libevdi 1.9.0, evdi_open_attached_to adds and opens a node in one call; since 1.14.3 the preferred function is evdi_open_attached_to_fixed.
  • USB parent linking A node can be linked to a USB device in sysfs by passing a parent descriptor such as usb:2-2.1. The documentation gives the example of linking /sys/bus/usb/devices/2-2.1/evdi.0 to the first platform EVDI device. This records the relationship between a virtual display and the USB hardware that drives it.
  • Connection with EDID and limits evdi_connect and evdi_connect2 tell the DRM subsystem that a monitor is attached and pass its EDID, which triggers a hot plug event. evdi_connect2 takes a maximum pixel area and a maximum pixel per second rate for the connected device. evdi_disconnect produces the matching unplug event.
  • Client-allocated frame buffers The library does not allocate memory for screen buffers. The client registers its own buffers with evdi_register_buffer, can register as many as it needs and refers to any of them in later update requests. Screen updates are requested and then copied into a buffer with the grab pixels call.
  • Asynchronous events The model is event driven: the client watches a file descriptor from evdi_get_event_ready and calls evdi_handle_events to dispatch notifications. Documented events are update ready, mode changed, DPMS power state, CRTC state change, cursor set and move, and DDC/CI data requests. The quickstart states that a device may become unresponsive if events and updates are not handled regularly.
  • Cursor handling modes By default the module composites the mouse cursor into the user-supplied frame buffer and raises an update event on each cursor change. With evdi_enable_cursor_events, the client receives cursor set and cursor move notifications instead and blends the cursor itself.
  • DDC/CI passthrough Each EVDI node also creates an i2c adapter. DDC/CI requests on address 0x37, used for settings such as brightness and contrast, are passed to user space as notifications, and the client answers with evdi_ddcci_response.
  • Module parameters and sysfs control The initial_device_count parameter sets how many EVDI devices are created when the module loads (default 0). Outputs can also be added by writing to /sys/devices/evdi/add, counted through /sys/devices/evdi/count and removed with /sys/devices/evdi/remove_all; adding and removing nodes requires root rights.
  • Logging callback Libevdi prints messages to stdout with printf by default. A client can install its own logging callback with evdi_set_logging and restore the default by passing a null callback.
  • API documentation The API details page documents every function, argument, return value and type, including evdi_handle, evdi_mode, evdi_buffer and evdi_event_context. A separate quickstart describes the structure of a typical client.
  • Tests and CI The repository includes KUnit tests for the module (DRM_EVDI_KUNIT_TEST), pytest tests for pyevdi, scripts to build against specific kernels and release candidates, a style check and a deb package test. Dev container definitions cover CentOS 9, CentOS 10 and Debian.
  • Source installation The top-level Makefile builds and installs the module, library and pyevdi with make and make install. The module README explains that manual installation does not write the modprobe and auto-load configuration that the DisplayLink installer creates.

Where EVDI fits

DisplayLink docks and adapters on Ubuntu

EVDI's main documented use is as the kernel side of the DisplayLink driver for Ubuntu. DisplayLink distributes the driver through its APT repository, a Launchpad PPA and a standalone .run installer, and the 6.4.0 release notes list Ubuntu 20.04, 22.04, 24.04, 25.04 and 26.04 with preliminary 26.10 support. The release notes describe the software as the open-source EVDI module and libevdi plus a binary user mode application for i686, amd64, armv7 and aarch64. DKMS is required for installation.

Packaging for other Linux distributions

DisplayLink states that it has not created drivers for other distributions, but that the open-source component of the Ubuntu driver is designed to be modified so the user community can repackage it. The README points to the community displaylink-rpm project for Fedora, CentOS Stream, Rocky Linux and AlmaLinux, and to the community evdi-dkms AUR package. Release 1.14.11 made the official EVDI deb package interchangeable with the community evdi-dkms and libevdi1 packages.

Writing a libevdi client

The quickstart describes the steps of a typical application: find or add a free EVDI node and open it, connect with the EDID of the monitor it represents, allocate and register buffers, then request and consume updates in a loop whenever the kernel signals that updates are ready. Notifications from the kernel module start right after connecting, and the quickstart uses them to size the buffers before updates are requested.

Adding a virtual output from the command line

The module README shows that an output can be created without a client by writing 1 to /sys/devices/evdi/add as root and checking /sys/devices/evdi/count. In an Xorg session, xrandr --listproviders then shows an additional modesetting provider, and xrandr --query lists a new disconnected output. Once a monitor is connected through EVDI, its resolutions are reported and graphical display tools show it.

Configuring the module for compositors

When the module is installed manually, the configuration written by the DisplayLink installer is missing. The module README describes two lines in /etc/modprobe.d/evdi.conf: initial_device_count, a workaround for X servers that build a static GPU list at startup, and a softdep rule that loads EVDI after the primary GPU driver so the compositor does not use EVDI as the primary GPU. The module is loaded at boot through /etc/modules-load.d/ or /etc/modules.

Testing and kernel development

Developers working on the module can enable the KUnit tests through the DRM_EVDI_KUNIT_TEST option and run the pyevdi pytest suite, which includes a sample 4K 60 Hz EDID. The CI scripts build the module against vanilla kernel sources and release candidates. The project accepts bug reports, feature requests and patches through GitHub issues and pull requests, and asks for help with distributions other than Ubuntu. Similar virtual display tools on other systems are listed on iThub: BetterDisplay for macOS and Staged for Windows 11.

Reviews of EVDI

No reviews yet

Be the first to share your experience with EVDI.

Loading review form…

Found EVDI useful? Upvote it todayYour vote helps other IT teams find it in the daily ranking.