No displays found when running mustash on device |
||||||
Issue descriptionWhen running mustash on device we no longer get any visual output. DrmNativeDisplayDelegate::GetDisplays() returns 0 displays when the callback fires so nothings gets drawn. Working: 10587cc6239040cc48e73db97d13dd3ee02afd85 (2 weeks ago) https://chromium.googlesource.com/chromium/src/+/10587cc6239040cc48e73db97d13dd3ee02afd85 Broken: fb20bb44c9677645d8dc35f27ba352b08d331b6d (5 days ago) https://chromium.googlesource.com/chromium/src/+/fb20bb44c9677645d8dc35f27ba352b08d331b6d
,
Nov 16 2016
,
Nov 22 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/89f115100afb5478a1da2c58baa5c0ef5852fd81 commit 89f115100afb5478a1da2c58baa5c0ef5852fd81 Author: sadrul <sadrul@chromium.org> Date: Tue Nov 22 19:15:30 2016 ozone-mus: Fix detecting displays on device in mustash. crrev.com/429173 introduces a separate OnGpuProcessLaunched() to GpuThreadObserver, which performs some of the initialization in the drm backend. Update the mus-proxy in ozone to make sure this new function is invoked in the observers before OnGpuThreadReady. BUG= 665544 Review-Url: https://codereview.chromium.org/2519283002 Cr-Commit-Position: refs/heads/master@{#433938} [modify] https://crrev.com/89f115100afb5478a1da2c58baa5c0ef5852fd81/ui/ozone/platform/drm/mus_thread_proxy.cc
,
Apr 3 2017
,
May 30 2017
,
Aug 1 2017
,
Jan 22 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by kylec...@chromium.org
, Nov 15 2016