From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
Gurchetan Singh <gurchetansingh@chromium.org>,
Rob Clark <robdclark@gmail.com>, Huang Rui <ray.huang@amd.com>,
Sergio Lopez <slp@redhat.com>,
Akihiko Odaki <akihiko.odaki@daynix.com>,
virtio-comment@lists.oasis-open.org
Subject: [virtio-comment] [PATCH v2 3/3] virtio-gpu: Update venus-protocol URL
Date: Fri, 15 Dec 2023 19:05:12 +0300 [thread overview]
Message-ID: <20231215160512.762757-3-dmitry.osipenko@collabora.com> (raw)
In-Reply-To: <20231215160512.762757-1-dmitry.osipenko@collabora.com>
The venus-protocol was moved to the main virgl gitlab group a year ago.
Update the link in the GPU documentation.
Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
---
device-types/gpu/description.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/device-types/gpu/description.tex b/device-types/gpu/description.tex
index 29c8a97c3a3f..e633787aacad 100644
--- a/device-types/gpu/description.tex
+++ b/device-types/gpu/description.tex
@@ -532,7 +532,7 @@ \subsubsection{Device Operation: controlq}\label{sec:Device Types / GPU Device /
the second edition of Virgl (Gallium OpenGL) protocol after the capset fix.
\item \href{https://android.googlesource.com/device/generic/vulkan-cereal/+/refs/heads/android13-release/protocols/vulkan/}{VIRTIO_GPU_CAPSET_GFXSTREAM_VULKAN} --
gfxtream's (mostly) autogenerated Vulkan streaming protocol.
- \item \href{https://gitlab.freedesktop.org/olv/venus-protocol}{VIRTIO_GPU_CAPSET_VENUS} --
+ \item \href{https://gitlab.freedesktop.org/virgl/venus-protocol}{VIRTIO_GPU_CAPSET_VENUS} --
Mesa's (mostly) autogenerated Vulkan protocol.
\item \href{https://chromium.googlesource.com/chromiumos/platform/crosvm/+/refs/heads/main/rutabaga_gfx/src/cross_domain/cross_domain_protocol.rs}{VIRTIO_GPU_CAPSET_CROSS_DOMAIN} --
protocol for display virtualization via Wayland proxying.
--
2.41.0
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
prev parent reply other threads:[~2023-12-15 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 16:05 [virtio-comment] [PATCH v2 1/3] virtio-gpu: Rename GFXSTREAM context capset to GFXSTREAM_VULKAN Dmitry Osipenko
2023-12-15 16:05 ` [virtio-comment] [PATCH v2 2/3] virtio-gpu: Document VIRTIO_GPU_CAPSET_DRM Dmitry Osipenko
2023-12-15 16:05 ` Dmitry Osipenko [this message]
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=20231215160512.762757-3-dmitry.osipenko@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=akihiko.odaki@daynix.com \
--cc=gurchetansingh@chromium.org \
--cc=kraxel@redhat.com \
--cc=ray.huang@amd.com \
--cc=robdclark@gmail.com \
--cc=slp@redhat.com \
--cc=virtio-comment@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).