search for: virtgpu_set_scanout

Displaying 7 results from an estimated 7 matches for "virtgpu_set_scanout".

2014 Sep 12
2
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...> + 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 and height. What if x, y, width, and height a...
2014 Sep 12
2
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...> + 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 and height. What if x, y, width, and height 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
...PU_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_t resource_id; + uint32_t width; + uint32_t height; + uint32_t x; + uint32_t y; +}; + +/* VIRTGPU_CMD_RESOURCE_FLUSH */ +struct virtgpu_resource_flush { + struct virtgpu_ctrl_hdr...
2014 Sep 12
0
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...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 > > + rectangle specified by x, y, width and height. >...
2014 Sep 11
0
[PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...of formats are support. The + resource ids are generated by the guest. + +VIRTGPU_CMD_RESOURCE_UNREF: + Command: struct virtgpu_resource_unref + + Destroy a resource. + + This informs the host that a resource is no longer required by the + guest. + +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 and height. + +VIRTGPU_CMD_RESOURCE_FLUSH: + Command: struct virtgpu_resour...