From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Hellstrom <thellstrom@vmware.com>
Subject: KMS cursor BO semantics
Date: Fri, 04 Nov 2011 12:59:59 +0100
Message-ID: <4EB3D3BF.70909@vmware.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org>
Received: from smtp-outbound-2.vmware.com (smtp-outbound-2.vmware.com
	[65.115.85.73])
	by gabe.freedesktop.org (Postfix) with ESMTP id CC1AE9E99F
	for <dri-devel@lists.freedesktop.org>;
	Fri,  4 Nov 2011 05:02:30 -0700 (PDT)
Received: from mailhost3.vmware.com (mailhost3.vmware.com [10.16.27.45])
	by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 84A2A51006
	for <dri-devel@lists.freedesktop.org>;
	Fri,  4 Nov 2011 05:02:30 -0700 (PDT)
Received: from linlap1.home.shipmail.org (unknown [10.23.99.61])
	by mailhost3.vmware.com (Postfix) with ESMTP id 64AB4CDABE
	for <dri-devel@lists.freedesktop.org>;
	Fri,  4 Nov 2011 05:02:28 -0700 (PDT)
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/dri-devel>
List-Post: <mailto:dri-devel@lists.freedesktop.org>
List-Help: <mailto:dri-devel-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=subscribe>
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
List-Id: dri-devel@lists.freedesktop.org

Hi.

I have a question about the semantics of the DRM_IOCTL_MODE_CURSOR iotcl:

Some hardware (vmware's virtual in particular) may not be able to pick 
up the changes from a bo directly, since the cursor data is sent though 
the command stream. Hence we need a notification when the cursor image 
has changed.

Could we *require* that a cursor image change needs to be followed by an 
ioctl call with the flag
DRM_MODE_CURSOR_BO?

Thanks,
Thomas