mirror of
https://gitlab.freedesktop.org/plymouth/plymouth.git
synced 2026-05-08 14:48:01 +02:00
read-only mirror of https://gitlab.freedesktop.org/plymouth/plymouth
33d5702de6
Right now a lot of pixel manipulation functions are in the frame buffer code. This means it's hard to do these types of things without the results showing up on the display. Furthermore, we want to get away from one frame buffer anyway for multihead support. I can imagine each display in a multihead configuration with its own pixel buffer, so splash plugins can draw to the independently. This commit adds the start of a pixel buffer class, which just copies and pastes most of pixel-twiddling frame buffer code. There are some changes to deal with pixel buffers not always having a final alpha of 1.0, and some changes to provide a more flexible interface for masking fill operations. At some point it will probably gain copy-and-pastes of the resize an rotate code from the image class as well, and provide a mechansim for have subpixbufs where rowstride != width. |
||
|---|---|---|
| images | ||
| scripts | ||
| src | ||
| themes | ||
| .gitignore | ||
| acinclude.m4 | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.ac | ||
| COPYING | ||
| INSTALL | ||
| Makefile.am | ||
| NEWS | ||
| README | ||
| TODO | ||
plymouth - graphical boot animation and logger Plymouth is an application that runs very early in the boot process (even before the root filesystem is mounted!) that provides a graphical boot animation while the boot process happens in the background. It is designed to work on systems with DRM modesetting drivers. The idea is that early on in the boot process the native mode for the computer is set, plymouth uses that mode, and that mode stays throughout the entire boot process up to and after X starts. Ideally, the goal is to get rid of all flicker during startup. For systems that don't have DRM mode settings drivers, plymouth falls back to text mode. In either text or graphics mode, the boot messages are completely occluded. After the root file system is mounted read-write, the messages are dumped to /var/log/boot.log. Also, the user can see the messages at any time during boot up by hitting the escape key. Plymouth isn't really designed to be built from source by end users. For it to work correctly, it needs integration with the distribution. Because it starts so early, it needs to be packed into the distribution's initial ram disk, and the distribution needs to poke plymouth to tell it how boot is progressing. plymouth ships with two binaries: /sbin/plymouthd and /bin/plymouth The first one, plymouthd, does all the heavy lifting. It logs the session and shows the splash screen. The second one, /bin/plymouth, is the control interface to plymouthd. It supports things like plymouth --show-splash, or plymouth --ask-for-password, which trigger the associated action in plymouthd. plymouth supports various "splash" plugins which are analagous to screensavers, but happen at boot time. Currently there are three graphical splash plugins: solar, fade-in, and spinfinity. There are also three non-graphical plugins which are for text mode and the detailed view. The graphical plugins need a logo image and background color to function. Distributions are expected to set these up in their packages at ./configure time, but there are some placeholder values set up if ./configure doesn't get those options. Plymouth isn't done yet. It's still under active development and isn't ready for distros to use as-is. That should change in the near future though.