diff options
| author | Toshiki Kikuchi <toshikikikuchi@google.com> | 2023-10-25 06:43:28 +0000 |
|---|---|---|
| committer | Android Build Cherrypicker Worker <android-build-cherrypicker-worker@google.com> | 2023-10-25 06:45:43 +0000 |
| commit | f6ba5cd2dbe5b363618325ff878dca4851066420 (patch) | |
| tree | 930d4930d16e4539227bd495b510d5e6cddd7b0d | |
| parent | bbf4f4a902609f900a00284ea573288dcd2833be (diff) | |
| download | wayland-protocols-f6ba5cd2dbe5b363618325ff878dca4851066420.tar.gz | |
Uprev remote-shell
This CL upgrades remote-shell.
Bug: 296950585
Test: m
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:dcfe0e9ad90f38e2e3ab5fbdd906ef5b64ea2184)
Merged-In: If4a84e6de3b907501179cd010e92f9b7ec5901c9
Change-Id: If4a84e6de3b907501179cd010e92f9b7ec5901c9
| -rw-r--r-- | chromium.org/unstable/remote-shell/remote-shell-unstable-v2.xml | 17 |
1 files changed, 16 insertions, 1 deletions
diff --git a/chromium.org/unstable/remote-shell/remote-shell-unstable-v2.xml b/chromium.org/unstable/remote-shell/remote-shell-unstable-v2.xml index dec0247..9c6733d 100644 --- a/chromium.org/unstable/remote-shell/remote-shell-unstable-v2.xml +++ b/chromium.org/unstable/remote-shell/remote-shell-unstable-v2.xml @@ -934,7 +934,7 @@ </request> </interface> - <interface name="zcr_toast_surface_v2" version="1"> + <interface name="zcr_toast_surface_v2" version="2"> <description summary="A toast window"> An interface that may be implemented by a wl_surface to host toast contents. @@ -968,6 +968,21 @@ <arg name="width" type="int"/> <arg name="height" type="int"/> </request> + + <!-- Version 2 additions --> + <request name="set_scale_factor" since="2"> + <description summary="Allows the client to set the scale factor for the future buffer commits."> + The client has a 32-bit float scale factor that is associated with each + remote surface. This scale factor must be propagated exactly to exo. To + do so we reinterpret_cast into a 32-bit uint and later cast back into a + float. This is because wayland does not support native transport of + floats. As different CPU architectures may use different endian + representations for IEEE 754 floats, this protocol implicitly assumes + that the caller and receiver are the same machine. + This is double buffered state and will be applied in the next commit. + </description> + <arg name="scale_factor_as_uint" type="uint"/> + </request> </interface> <interface name="zcr_remote_output_v2" version="1"> |