Date: Fri, 11 Aug 2023 15:33:25 +0200 From: Jan Beich <jbeich@FreeBSD.org> To: x11@FreeBSD.org Subject: DRM in base, again? Message-ID: <fs4p-snyy-wny@FreeBSD.org>
next in thread | raw e-mail | index | archive | help
Having drm-kmod live in ports/ has problems: - LinuxKPI sometimes breaking KBI on X.Y -> X.Y+1 upgrades which affects binary packages during 3 months when both X.Y and X.Y+1 are supported - No uAPI thus Mesa, wlroots, chromium, etc. have to bundle <linux/dma-buf.h> - No KPI thus nvidia-drm has to bundle drm-kmod unlike other *-kmod ports and points of confusion: - When drm-kmod was introduced it was supposed to evolve faster than FreeBSD but due unstable KPI upstream and lack of manpower to maintain conditionals only one drm-kmod for a given -RELEASE was usually supported. - While drm-kmod versions match Linux versions, FreeBSD support model[1] makes it easy to pick a wrong FreeBSD version as kernel is rarely upgraded independently from OS thus old major versions often cannot support newer GPUs (except NVIDIA). For example, FreeBSD release notes could document supported GPUs to help users decide. What's current status? Is it too late for the upcoming 14.0-RELEASE? https://reviews.freebsd.org/D23085 and https://github.com/evadot/drm-subtree appear inactive and limited to non-x86 drivers. -- [1] For comparison, OpenBSD releases twice a year from HEAD, bringing newer WiFi and GPU drivers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fs4p-snyy-wny>