diff options
| author | Gurchetan Singh <gurchetansingh@chromium.org> | 2019-03-25 17:24:52 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2019-03-26 17:27:02 -0700 |
| commit | 5aaa63f50800e241d1ad354c37792983b159ec1f (patch) | |
| tree | a48fae02feb15c49fb84114abc1e511ec793dafa /devices/src/virtio | |
| parent | 348df2dbf7fc36dcddc9368ff2c34b18c69765ce (diff) | |
| download | crosvm-5aaa63f50800e241d1ad354c37792983b159ec1f.tar crosvm-5aaa63f50800e241d1ad354c37792983b159ec1f.tar.gz crosvm-5aaa63f50800e241d1ad354c37792983b159ec1f.tar.bz2 crosvm-5aaa63f50800e241d1ad354c37792983b159ec1f.tar.lz crosvm-5aaa63f50800e241d1ad354c37792983b159ec1f.tar.xz crosvm-5aaa63f50800e241d1ad354c37792983b159ec1f.tar.zst crosvm-5aaa63f50800e241d1ad354c37792983b159ec1f.zip | |
devices: gpu: use render optimized buffers
Using non-linear buffer seems to be safe based on the apps I've
tested. This is similiar to the ARC++ use case, which also doesn't
explicitly send modifiers to Chrome.
BUG=chromium:945033
TEST=clear_clear goes from 980 mpixels --> 6797.90 mpixels
on Nami
Change-Id: I2dcb78366c2d2d83d64bb23f6da1f07c8747819c
Reviewed-on: https://chromium-review.googlesource.com/1538463
Commit-Ready: Gurchetan Singh <gurchetansingh@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>
Reviewed-by: David Riley <davidriley@chromium.org>
Reviewed-by: Chia-I Wu <olv@google.com>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Diffstat (limited to 'devices/src/virtio')
| -rw-r--r-- | devices/src/virtio/gpu/backend.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/devices/src/virtio/gpu/backend.rs b/devices/src/virtio/gpu/backend.rs index fad8223..ea7faff 100644 --- a/devices/src/virtio/gpu/backend.rs +++ b/devices/src/virtio/gpu/backend.rs @@ -764,7 +764,7 @@ impl Backend { width, height, Format::from(fourcc), - Flags::empty().use_scanout(true).use_linear(true), + Flags::empty().use_scanout(true).use_rendering(true), ) { Ok(buffer) => buffer, Err(e) => { |