On Tue, Sep 1, 2026 at 4:28 AM Akihiko Odaki <[email protected]>
wrote:

> Rutabaga was externalized from crosvm:
>
> https://chromium.googlesource.com/crosvm/crosvm/+/481338d967d5c8b506e17b8e335798f5cb89d7ee
>
> Signed-off-by: Akihiko Odaki <[email protected]>
> ---
>  docs/system/devices/virtio/virtio-gpu.rst | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/docs/system/devices/virtio/virtio-gpu.rst
> b/docs/system/devices/virtio/virtio-gpu.rst
> index d05f8cb8e3f9..8ce4da306acd 100644
> --- a/docs/system/devices/virtio/virtio-gpu.rst
> +++ b/docs/system/devices/virtio/virtio-gpu.rst
> @@ -185,8 +185,9 @@ rendering and `Wayland display passthrough`_.  With
> the gfxstream rendering
>  mode, GLES and Vulkan calls are forwarded to the host with minimal
>  modification.
>
> -The crosvm book provides directions on how to build a `gfxstream-enabled
> -rutabaga`_ and launch a `guest Wayland proxy`_.
> +rutabaga_gfx's documentation provides directions on how to build a
> +`gfxstream-enabled rutabaga`_. The crosvm book provides directions on
> +how to launch a `guest Wayland proxy`_.
>
>  This device does require host blob support (``hostmem`` field below). The
>  ``hostmem`` field specifies the size of virtio-gpu host memory window.
> @@ -214,7 +215,7 @@ Surfaceless is the default if ``wsi`` is not specified.
>
>  .. _gfxstream:
> https://android.googlesource.com/platform/hardware/google/gfxstream/


nit: gfxstream link is also incorrect:

https://github.com/google/gfxstream

now


>
>  .. _Wayland display passthrough:
> https://www.youtube.com/watch?v=OZJiHMtIQ2M
> -.. _gfxstream-enabled rutabaga:
> https://crosvm.dev/book/appendix/rutabaga_gfx.html
> +.. _gfxstream-enabled rutabaga:
> https://github.com/magma-gpu/rutabaga_gfx#rutabaga-c-api
>  .. _guest Wayland proxy: https://crosvm.dev/book/devices/wayland.html
>
>  .. list-table:: Linux Host Requirements
>
> ---
> base-commit: d2e570cc0f97b936902a5b1b86b73c0f5998b475
> change-id: 20260801-crosvm-658027011cb5
>
> Best regards,
> --
> Akihiko Odaki <[email protected]>
>
>
>

Reply via email to