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

Issue 642540 link

Starred by 4 users

Issue metadata

Status: Verified
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue 581462
issue 731255



Sign in to add a comment

Remove BootSplashScreen

Project Member Reported by msw@chromium.org, Aug 30 2016

Issue description

Support Chrome OS boot screen in mus/mash.

One difficulty of porting BootSplashScreen is its ui::CopyAreaToCanvas call, which uses gfx::AcceleratedWidget:
https://cs.chromium.org/chromium/src/ash/wm/boot_splash_screen_chromeos.cc?rcl=0&l=46

This hopefully won't block other mash wallpaper progress ( Issue 629605 ), I can probably punt this aspect.
(it's partly related to wallpaper code; see RootWindowController::CreateSystemWallpaper)
 

Comment 1 by derat@chromium.org, Aug 30 2016

Cc: marc...@chromium.org reve...@chromium.org
AFAIK: we agreed that mus doesn't need to support CrOS/X11 on devices. I'll figure out how MUS should do this. My understanding from marcheu@ is that for ozone drm devices, this is done externally to Chrome.
The code you are looking at is for X11 only, and as you say we don't care about it for Chrome OS.

For some reason, the splash screen copy is implemented differently for ozone drm than for X11 (it is implemented directly inside of ozone).

See src/ui/ozone/platform/drm/gpu/drm_console_buffer.cc which does get the existing framebuffer (from the splash screen) and copies it into a skia surface. Also see screen_manager.cc which calls into this from FillModesetBuffer().
Owner: rjkroege@chromium.org
Status: Available (was: Untriaged)
Labels: -Proj-Mustash-Mus Proj-Mustash-Mus-GPU Proj-Mustash-Milestone-Tadpole
Blocking: 581462

Comment 7 by sky@chromium.org, Mar 27 2017

Labels: mustash-2

Comment 8 by sky@chromium.org, Jun 8 2017

Blocking: 731255
Owner: sky@chromium.org
sky@: perhaps you could find someone else to validate that this bug exists and/or has been fixed for mushrome?

Comment 10 by sky@chromium.org, Aug 22 2017

Status: Started (was: Available)
Summary: Remove BootSplashScreen (was: Support Chrome OS boot screen in mus/mash.)
With the switch to ozone this code is effectively dead and can be removed.

Comment 11 by derat@chromium.org, Aug 22 2017

I should delete the fade_boot_splash_screen USE flag and associated code as well.
Project Member

Comment 12 by bugdroid1@chromium.org, Aug 23 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/8995b2087a64fbb2d987b6d03d5bd03b88f237b3

commit 8995b2087a64fbb2d987b6d03d5bd03b88f237b3
Author: Daniel Erat <derat@chromium.org>
Date: Wed Aug 23 07:04:08 2017

login: Remove login-animation-related USE flags.

Remove code that checks for the old, unused
disable_login_animations and fade_boot_splash_screen USE
flags.

BUG= chromium:642540 
TEST=none

Change-Id: I6c547b8d362dc106d26aa06a2e8d3c7c559f714b
Reviewed-on: https://chromium-review.googlesource.com/627667
Commit-Ready: Dan Erat <derat@chromium.org>
Tested-by: Dan Erat <derat@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/8995b2087a64fbb2d987b6d03d5bd03b88f237b3/login_manager/chrome_setup.cc

Project Member

Comment 13 by bugdroid1@chromium.org, Aug 23 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/8e4823774f1f7a73e6b92165bbf98f8bf8f2e566

commit 8e4823774f1f7a73e6b92165bbf98f8bf8f2e566
Author: Daniel Erat <derat@chromium.org>
Date: Wed Aug 23 09:02:39 2017

libchromeos-use-flags: Remove obsolete boot animation flags.

Remove the disable_login_animations and
fade_boot_splash_screen USE flags, which correspond to
dead/removed code in Chrome.

BUG= chromium:642540 
TEST=none

Change-Id: Ib54680ac22a9266043a45d35751181f2bee91b6d
Reviewed-on: https://chromium-review.googlesource.com/627666
Commit-Ready: Dan Erat <derat@chromium.org>
Tested-by: Dan Erat <derat@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[rename] https://crrev.com/8e4823774f1f7a73e6b92165bbf98f8bf8f2e566/chromeos-base/libchromeos-use-flags/libchromeos-use-flags-0.0.1-r36.ebuild
[modify] https://crrev.com/8e4823774f1f7a73e6b92165bbf98f8bf8f2e566/chromeos-base/libchromeos-use-flags/libchromeos-use-flags-0.0.1.ebuild

Comment 15 by sky@chromium.org, Aug 23 2017

Dan, is there anything else to remove in ChromeOS repos? Should I marked this fixed?
Project Member

Comment 16 by bugdroid1@chromium.org, Aug 23 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/e2db758f74ecb9db892b9385a73927db7451ed05

commit e2db758f74ecb9db892b9385a73927db7451ed05
Author: Daniel Erat <derat@chromium.org>
Date: Wed Aug 23 21:18:05 2017

overlays: Remove obsolete login animation USE flags.

Remove the disable_login_animations USE flag from x86-alex,
x86-mario, and x86-zgb, and fade_boot_splash_screen from
lumpy. These correspond to dead/removed code in Chrome.

BUG= chromium:642540 
TEST=none

Change-Id: Ida17c91c867daec174a253aad9199f5018b69a1c
Reviewed-on: https://chromium-review.googlesource.com/627665
Tested-by: Dan Erat <derat@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/e2db758f74ecb9db892b9385a73927db7451ed05/overlay-lumpy/profiles/base/make.defaults
[modify] https://crrev.com/e2db758f74ecb9db892b9385a73927db7451ed05/overlay-x86-zgb/profiles/base/make.defaults
[modify] https://crrev.com/e2db758f74ecb9db892b9385a73927db7451ed05/overlay-x86-alex/profiles/base/make.defaults
[modify] https://crrev.com/e2db758f74ecb9db892b9385a73927db7451ed05/overlay-x86-mario/profiles/base/make.defaults

Comment 17 by derat@chromium.org, Aug 23 2017

Status: Verified (was: Started)
I think that should be it -- thanks!

Comment 18 by sky@chromium.org, Aug 23 2017

Thank you for the help and cleanup in the ChromeOS repos.

Sign in to add a comment