NetBSD Problem Report #60678

From www@netbsd.org  Wed Sep  2 13:58:20 2026
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits)
	 client-signature RSA-PSS (2048 bits))
	(Client CN "mail.netbsd.org", Issuer "YR1" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 58AA81A923B
	for <gnats-bugs@gnats.NetBSD.org>; Wed,  2 Sep 2026 13:58:20 +0000 (UTC)
Message-Id: <20260902135819.8B9891A923C@mollari.NetBSD.org>
Date: Wed,  2 Sep 2026 13:58:19 +0000 (UTC)
From: jiaxun.yang@flygoat.com
Reply-To: jiaxun.yang@flygoat.com
To: gnats-bugs@NetBSD.org
Subject: WSDISPLAYIO Damage reporting support
X-Send-Pr-Version: www-1.0
X-From4GNATS: "jiaxun.yang@flygoat.com via gnats" <gnats-admin@NetBSD.org>

>Number:         60678
>Category:       xsrc
>Synopsis:       WSDISPLAYIO Damage reporting support
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    xsrc-manager
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Sep 02 14:00:01 +0000 2026
>Originator:     Jiaxun Yang
>Release:        current
>Organization:
>Environment:
>Description:
WSDISPLAY lacks a generic damage reporting mechnisim, and thus display drivers that requires notification for changes on framebuffer content.

Currently, viogpu can't expose dumbfb support due to that, and udlfb is using a very ineffcient way to scan diffs on framebuffer.
>How-To-Repeat:
wsfb X won't work with viogpu driver.
>Fix:
I have a proposal:

https://mail-index.netbsd.org/tech-kern/2025/05/12/msg030435.html

And corresponding implementation:
https://github.com/NetBSD/src/pull/86
https://github.com/NetBSD/xsrc/pull/1

Home	PR Database Search