[automerger skipped] Uprev remote-shell and aura-shell am: bbf4f4a902 am: a8763d62ea -s ours
am skip reason: Merged-In I048d5c73d72d29fe98d6270e8ede3399ddf5ba0a with SHA-1 bbf4f4a902 is already in history
Original change: https://android-review.googlesource.com/c/platform/external/wayland-protocols/+/2803613
Change-Id: Icf948e781f479b8391b7edd55a26fda8b38879c5
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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">
