Displaying 7 results from an estimated 7 matches for "virtgpu_cmd_set_scanout".
2014 Sep 12
2
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...> + Create a 2D resource on the host.
> +
> + This creates a 2D resource on the host with the specified width,
> + height and format. Only a small subset of formats are support. The
> + resource ids are generated by the guest.
Can the host refuse due to lack of resources?
> +VIRTGPU_CMD_SET_SCANOUT:
> + Command: struct virtgpu_set_scanout
> +
> + Set the scanout parameters for a single output.
> +
> + This sets the scanout parameters for a single scanout. The
> + resource_id is the resource to be scanned out from, along with a
> + rectangle specified by x, y, width a...
2014 Sep 12
2
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...> + Create a 2D resource on the host.
> +
> + This creates a 2D resource on the host with the specified width,
> + height and format. Only a small subset of formats are support. The
> + resource ids are generated by the guest.
Can the host refuse due to lack of resources?
> +VIRTGPU_CMD_SET_SCANOUT:
> + Command: struct virtgpu_set_scanout
> +
> + Set the scanout parameters for a single output.
> +
> + This sets the scanout parameters for a single scanout. The
> + resource_id is the resource to be scanned out from, along with a
> + rectangle specified by x, y, width a...
2014 Sep 11
9
[PATCH 0/2] virtio-gpu: hardware specification
Hi folks,
Lets kick off the virtio-gpu review process, starting with the virtio
protocol.
This is a tiny patch series for qemu. Patch #1 carries the header file
describing the virtual hardware: config space, command structs being
sent over the rings, defines etc. Patch #2 adds a text file describing
virtio-gpu to docs/specs/. It covers 2D support only for now.
For anybody who wants to dig a
2014 Sep 11
9
[PATCH 0/2] virtio-gpu: hardware specification
Hi folks,
Lets kick off the virtio-gpu review process, starting with the virtio
protocol.
This is a tiny patch series for qemu. Patch #1 carries the header file
describing the virtual hardware: config space, command structs being
sent over the rings, defines etc. Patch #2 adds a text file describing
virtio-gpu to docs/specs/. It covers 2D support only for now.
For anybody who wants to dig a
2014 Sep 11
0
[PATCH 1/2] virtio-gpu/2d: add hardware spec include file
.../virtgpu_hw.h
@@ -0,0 +1,158 @@
+#ifndef VIRTGPU_HW_H
+#define VIRTGPU_HW_H
+
+enum virtgpu_ctrl_type {
+ VIRTGPU_UNDEFINED = 0,
+
+ /* 2d commands */
+ VIRTGPU_CMD_GET_DISPLAY_INFO = 0x0100,
+ VIRTGPU_CMD_RESOURCE_CREATE_2D,
+ VIRTGPU_CMD_RESOURCE_UNREF,
+ VIRTGPU_CMD_SET_SCANOUT,
+ VIRTGPU_CMD_RESOURCE_FLUSH,
+ VIRTGPU_CMD_TRANSFER_TO_HOST_2D,
+ VIRTGPU_CMD_RESOURCE_ATTACH_BACKING,
+ VIRTGPU_CMD_RESOURCE_INVAL_BACKING,
+
+ /* cursor commands */
+ VIRTGPU_CMD_UPDATE_CURSOR = 0x0300,
+ VIRTGPU_CMD_MOVE_CURSOR,
+
+ /* su...
2014 Sep 12
0
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...?
Yes. virtgpu_ctrl_hdr.type in the response will be set to
VIRTGPU_RESP_ERR_* then. Current implementation does that only on
malloc() failure, there is no accounting (yet) to limit the amout of
memory the guest is allowed to allocate.
/me notes to write a section on error handling.
> > +VIRTGPU_CMD_SET_SCANOUT:
> > + Command: struct virtgpu_set_scanout
> > +
> > + Set the scanout parameters for a single output.
> > +
> > + This sets the scanout parameters for a single scanout. The
> > + resource_id is the resource to be scanned out from, along with a
> > + r...
2014 Sep 11
0
[PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...king store to the resources in order for DMA transfers to
+work. This is like a GART in a real GPU.
+
+A typical guest user would create a 2D resource using
+VIRTGPU_CMD_RESOURCE_CREATE_2D, attach backing store using
+VIRTGPU_CMD_RESOURCE_ATTACH_BACKING, then attach the resource to a
+scanout using VIRTGPU_CMD_SET_SCANOUT, then use
+VIRTGPU_CMD_TRANSFER_SEND_2D to send updates to the resource, and
+finally VIRTGPU_CMD_RESOURCE_FLUSH to flush the scanout buffers to
+screen.
+
+
+control queue commands (2D)
+---------------------------
+
+VIRTGPU_CMD_GET_DISPLAY_INFO:
+ Command: none (just struct virtgpu_ctrl_hdr).
+...