All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] [PATCH] virtio-gpu: some edid clarifications
Date: Mon, 2 Dec 2019 12:00:17 -0500	[thread overview]
Message-ID: <20191202115913-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20191128114243.23511-1-kraxel@redhat.com>

On Thu, Nov 28, 2019 at 12:42:43PM +0100, Gerd Hoffmann wrote:
> Add some notes about fetching the EDID information.
> 
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>

As a minor nit, it is preferable to send spec patches on virtio-comment.

virtio-dev is for code patches (implementation development).


> ---
>  virtio-gpu.tex | 13 +++++++++----
>  1 file changed, 9 insertions(+), 4 deletions(-)
> 
> diff --git a/virtio-gpu.tex b/virtio-gpu.tex
> index af4ca610d235..15dbf9f2ec82 100644
> --- a/virtio-gpu.tex
> +++ b/virtio-gpu.tex
> @@ -70,16 +70,21 @@ \subsubsection{Events}
>  \begin{description}
>  \item[VIRTIO_GPU_EVENT_DISPLAY] Display configuration has changed.
>    The driver SHOULD use the VIRTIO_GPU_CMD_GET_DISPLAY_INFO command to
> -  fetch the information from the device.
> +  fetch the information from the device.  In case EDID support is
> +  negotiated (VIRTIO_GPU_F_EDID feature flag) the device SHOULD also
> +  fetch the updated EDID blobs using the VIRTIO_GPU_CMD_GET_EDID
> +  command.
>  \end{description}
>  
>  \devicenormative{\subsection}{Device Initialization}{Device Types / GPU Device / Device Initialization}
>  
>  The driver SHOULD query the display information from the device using
>  the VIRTIO_GPU_CMD_GET_DISPLAY_INFO command and use that information
> -for the initial scanout setup.  In case no information is available or
> -all displays are disabled the driver MAY choose to use a fallback,
> -such as 1024x768 at display 0.
> +for the initial scanout setup.  In case EDID support is negotiated
> +(VIRTIO_GPU_F_EDID feature flag) the device SHOULD also fetch the EDID
> +information using the VIRTIO_GPU_CMD_GET_EDID command.  If no
> +information is available or all displays are disabled the driver MAY
> +choose to use a fallback, such as 1024x768 at display 0.
>  
>  \subsection{Device Operation}\label{sec:Device Types / GPU Device / Device Operation}
>  
> -- 
> 2.18.1
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2019-12-02 17:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28 11:42 [virtio-dev] [PATCH] virtio-gpu: some edid clarifications Gerd Hoffmann
2019-12-02 17:00 ` Michael S. Tsirkin [this message]
2019-12-03  9:35 ` [virtio-dev] " Gerd Hoffmann
2020-02-27 15:33   ` Michael S. Tsirkin

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=20191202115913-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=virtio-dev@lists.oasis-open.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.