From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Pratik Parvati <pratikp@vayavyalabs.com>, qemu-devel@nongnu.org
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: Virtio-GPU Xres and Yres seettings
Date: Mon, 20 Dec 2021 09:55:00 +0100 [thread overview]
Message-ID: <aedfa17d-6d31-6d5d-b367-cf84e77d27ed@redhat.com> (raw)
In-Reply-To: <CA+aXn+EZQ=S+P=8fyfCxYikEMLLdqAEeQgi580Tqtsuot-r2dw@mail.gmail.com>
Cc'ing Gerd & Marc-André.
On 12/20/21 05:26, Pratik Parvati wrote:
> Hi Team,
>
> I am working on a Virtio-GPU device (backend) for one of our customer
> projects - we are using the Virtio-GPU driver (frontend) to drive our
> device. Our device code has been written using Qemu virtio-gpu device
> code as a reference. Our device is setting the resolution to 1024x768 as
> a response to the command received from the driver (i.e,
> VIRTIO_GPU_CMD_GET_DISPLAY_INFO) - I also verified that driver is
> receiving the response bytes properly, but the next
> command (i.e, VIRTIO_GPU_CMD_RESOURCE_CREATE_2D) that device receive has
> a width and height as 4096 and 2160 respectively. The driver is assuming
> a 4k display for some reason and I need your help to understand why this
> is happening.
>
> Our display is corrupted for the same Xres and Yres misunderstanding
> between the device and the driver - Please guide me to understand the
> problem. Let me know if you have any questions or need more information.
>
> Thanks & Regards,
> Pratik
next prev parent reply other threads:[~2021-12-20 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 4:26 Virtio-GPU Xres and Yres seettings Pratik Parvati
2021-12-20 8:55 ` Philippe Mathieu-Daudé [this message]
2021-12-20 10:35 ` Gerd Hoffmann
2021-12-20 12:03 ` Pratik Parvati
2021-12-20 12:18 ` Gerd Hoffmann
2021-12-20 17:14 ` Pratik Parvati
2021-12-21 11:11 ` Gerd Hoffmann
2021-12-21 11:27 ` Pratik Parvati
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aedfa17d-6d31-6d5d-b367-cf84e77d27ed@redhat.com \
--to=philmd@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pratikp@vayavyalabs.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).