All of lore.kernel.org
 help / color / mirror / Atom feed
* [virtio-dev] [PATCH] virtio-gpu: some edid clarifications
@ 2019-11-28 11:42 Gerd Hoffmann
  2019-12-02 17:00 ` Michael S. Tsirkin
  2019-12-03  9:35 ` [virtio-dev] " Gerd Hoffmann
  0 siblings, 2 replies; 4+ messages in thread
From: Gerd Hoffmann @ 2019-11-28 11:42 UTC (permalink / raw)
  To: virtio-dev; +Cc: Gerd Hoffmann

Add some notes about fetching the EDID information.

Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
 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


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [virtio-dev] [PATCH] virtio-gpu: some edid clarifications
  2019-11-28 11:42 [virtio-dev] [PATCH] virtio-gpu: some edid clarifications Gerd Hoffmann
@ 2019-12-02 17:00 ` Michael S. Tsirkin
  2019-12-03  9:35 ` [virtio-dev] " Gerd Hoffmann
  1 sibling, 0 replies; 4+ messages in thread
From: Michael S. Tsirkin @ 2019-12-02 17:00 UTC (permalink / raw)
  To: Gerd Hoffmann; +Cc: virtio-dev

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [virtio-dev] Re: [PATCH] virtio-gpu: some edid clarifications
  2019-11-28 11:42 [virtio-dev] [PATCH] virtio-gpu: some edid clarifications Gerd Hoffmann
  2019-12-02 17:00 ` Michael S. Tsirkin
@ 2019-12-03  9:35 ` Gerd Hoffmann
  2020-02-27 15:33   ` Michael S. Tsirkin
  1 sibling, 1 reply; 4+ messages in thread
From: Gerd Hoffmann @ 2019-12-03  9:35 UTC (permalink / raw)
  To: virtio-dev

On Thu, Nov 28, 2019 at 12:42:43PM +0100, Gerd Hoffmann wrote:
> Add some notes about fetching the EDID information.

https://github.com/oasis-tcs/virtio-spec/issues/64

cheers,
  Gerd


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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [virtio-dev] Re: [PATCH] virtio-gpu: some edid clarifications
  2019-12-03  9:35 ` [virtio-dev] " Gerd Hoffmann
@ 2020-02-27 15:33   ` Michael S. Tsirkin
  0 siblings, 0 replies; 4+ messages in thread
From: Michael S. Tsirkin @ 2020-02-27 15:33 UTC (permalink / raw)
  To: Gerd Hoffmann; +Cc: virtio-dev

On Tue, Dec 03, 2019 at 10:35:10AM +0100, Gerd Hoffmann wrote:
> On Thu, Nov 28, 2019 at 12:42:43PM +0100, Gerd Hoffmann wrote:
> > Add some notes about fetching the EDID information.
> 
> https://github.com/oasis-tcs/virtio-spec/issues/64
> 
> cheers,
>   Gerd


I pushed it now but it all needed a bunch of manual tweaking.
Gerd I'd appreciate it if you follow the process described
in README.md section "Use of github issues" in the future. Thanks!

> 
> ---------------------------------------------------------------------
> 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


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2020-02-27 15:33 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-11-28 11:42 [virtio-dev] [PATCH] virtio-gpu: some edid clarifications Gerd Hoffmann
2019-12-02 17:00 ` Michael S. Tsirkin
2019-12-03  9:35 ` [virtio-dev] " Gerd Hoffmann
2020-02-27 15:33   ` Michael S. Tsirkin

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.