New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 609319 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug
mus

Blocking:
issue 609317



Sign in to add a comment

Implement Mojo interface for Gpu, GpuHost, Media, Ozone.

Project Member Reported by fsam...@chromium.org, May 4 2016

Issue description

In the limit, all subcomponents of the Gpu service should have Mojo interfaces. This is a bug to track progress toward that goal.

 
Summary: Implement Mojo interface for Gpu, GpuHost, Media, Ozone. (was: Implement Mojo interface for Gpu, GpuHost Media, Ozone.)
Labels: tadpole
Owner: fsam...@chromium.org
Status: Assigned (was: Untriaged)
fsamuel@ can you make this bug more precise?
This is really trying to capture the fact that Mus tadpole currently is not actually pure mojo. We should make progress toward pure mojo.
So I agree... but my ask here is to clarify what would constitute marking the bug "fixed".

Cc: j.iso...@samsung.com
Components: MUS
Components: Internals>MUS
Labels: Proj-Mustash
Status: WontFix (was: Assigned)
This bug is way too generic and beyond the scope of what we wish to accomplish in the short term. I'm marking as WONTFIX
Components: -Internals>MUS Internals>Services>WindowService
Components: -MUS

Sign in to add a comment