New issue
Advanced search Search tips

Issue 756941 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Sep 17
Cc:
rjkroege@chromium.org
sky@chromium.org
mustash-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Fix simple display management initialization

Project Member Reported by kylec...@chromium.org, Aug 18 2017 
 Issue 736815  was caused by some sort of a race that caused ash to be initialized without any displays. Ash was fixed to start correctly in headless mode, so this is low priority, but I think the sync call from ash::Shell::Init() to the WS needs to be fixed in general. Maybe we can avoid the sync call altogether?

Comment 1 by rjkroege@chromium.org, Aug 18 2017 

we could change simple display management like this:

* create a NDD mojom and implement directly in DrmThread (largely gutting DrmDisplayHost of display related functionality)
* give mus an api to obtain a "NDDPtr"
* mus would use the NDDPtr directly on start for display size inquiry
* ash would use the "transfer the NDDPtr to me" API to transfer the NDDPtr from mus to ash.

Comment 2 by jamescook@chromium.org, Apr 19 2018

Components: Internals>Services>Ash
Labels: -Proj-Mustash-Mash-WM

Comment 3 by jamescook@chromium.org, Apr 24 2018

Labels: -Proj-Mustash-Mus-WS
Deprecating Proj-Mustash-Mus-WS label in favor of Components.

Comment 4 by kylec...@chromium.org, Sep 17

Status: WontFix (was: Available)
►

Sign in to add a comment