Displaying 7 results from an estimated 7 matches for "virtgpu_resource_create_2d".
2014 Sep 12
2
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...guest must DMA transfer into these resources. This is a
> +design requirement in order to interface with future 3D rendering. In
> +the unaccelerated there is no support for DMA transfers from
"the unaccelerated case"?
> +VIRTGPU_CMD_RESOURCE_CREATE_2D:
> + Command: struct virtgpu_resource_create_2d
> +
> + 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?...
2014 Sep 12
2
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...guest must DMA transfer into these resources. This is a
> +design requirement in order to interface with future 3D rendering. In
> +the unaccelerated there is no support for DMA transfers from
"the unaccelerated case"?
> +VIRTGPU_CMD_RESOURCE_CREATE_2D:
> + Command: struct virtgpu_resource_create_2d
> +
> + 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?...
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
...ate only */
+};
+
+/* data passed in the control vq, 2d related */
+
+/* VIRTGPU_CMD_RESOURCE_UNREF */
+struct virtgpu_resource_unref {
+ struct virtgpu_ctrl_hdr hdr;
+ uint32_t resource_id;
+};
+
+/* VIRTGPU_CMD_RESOURCE_CREATE_2D: create a simple 2d resource with a format */
+struct virtgpu_resource_create_2d {
+ struct virtgpu_ctrl_hdr hdr;
+ uint32_t resource_id;
+ uint32_t format;
+ uint32_t width;
+ uint32_t height;
+};
+
+/* VIRTGPU_CMD_SET_SCANOUT */
+struct virtgpu_set_scanout {
+ struct virtgpu_ctrl_hdr hdr;
+ uint32_t scanout_id;
+ uint32_...
2014 Sep 12
0
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...The short-term goal for this text is to help reviewing the code by
documenting how the device is supposed to work. Being good enough for
an independent implementation is the next level. I'll keep it on the
radar though.
> > +VIRTGPU_CMD_RESOURCE_CREATE_2D:
> > + Command: struct virtgpu_resource_create_2d
> > +
> > + 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 t...
2014 Sep 11
0
[PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...screen.
+
+
+control queue commands (2D)
+---------------------------
+
+VIRTGPU_CMD_GET_DISPLAY_INFO:
+ Command: none (just struct virtgpu_ctrl_hdr).
+ Returns: struct virtgpu_resp_display_info.
+
+ Retrieve the current output configuration.
+
+VIRTGPU_CMD_RESOURCE_CREATE_2D:
+ Command: struct virtgpu_resource_create_2d
+
+ 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.
+
+VIRTGPU_CMD_RESOURCE_UNREF:
+ Command: struct virtgpu_resource_unref
+
+...