[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230227063821.dg2gbjjwcekbxyzw@sirius.home.kraxel.org>
Date: Mon, 27 Feb 2023 07:38:21 +0100
From: Gerd Hoffmann <kraxel@...hat.com>
To: Rob Clark <robdclark@...il.com>
Cc: dri-devel@...ts.freedesktop.org, Chia-I Wu <olvaffe@...il.com>,
Ryan Neph <ryanneph@...omium.org>,
Dmitry Osipenko <dmitry.osipenko@...labora.com>,
Rob Clark <robdclark@...omium.org>,
David Airlie <airlied@...hat.com>,
Gurchetan Singh <gurchetansingh@...omium.org>,
Daniel Vetter <daniel@...ll.ch>,
"open list:VIRTIO GPU DRIVER"
<virtualization@...ts.linux-foundation.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drm/virtio: Add option to disable KMS support
On Fri, Feb 24, 2023 at 10:02:24AM -0800, Rob Clark wrote:
> From: Rob Clark <robdclark@...omium.org>
>
> Add a build option to disable modesetting support. This is useful in
> cases where the guest only needs to use the GPU in a headless mode, or
> (such as in the CrOS usage) window surfaces are proxied to a host
> compositor.
Why make that a compile time option? There is a config option for the
number of scanouts (aka virtual displays) a device has. Just set that
to zero (and fix the driver to not consider that configuration an
error).
take care,
Gerd
Powered by blists - more mailing lists