summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/psplash/files/psplash-init
AgeCommit message (Collapse)Author
2020-02-25psplash: add systemd supportStefan Agner
Make use of the recently added systemd support in psplash. The utility psplash-systemd communicates boot progress to the splash screen. The splash is disabled once systemd consideres the system fully booted (progress is at 1.0). Note that this can take a while if systemd is stuck on a failing unit. This change adds two systemd services. One service starts psplash itself (psplash-start.service) and the second service starts the helper utility psplash-systemd (psplash-systemd.service). The units are written such that psplash-systemd.service can be used indepenendenly. This is useful when starting psplash in initramfs (not using systemd). Signed-off-by: Stefan Agner <stefan.agner@toradex.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-11-05psplash: Do mount psplash tmpfs if not mountedTorbjörn Svensson
The change in 5cea0448c5c75b9defc5fc2582e9b0c14e26a4e9 cases the following to be printed during boot: /etc/rcS.d/S00psplash.sh: line 28: [: -q: binary operator expected and the volume is thus never mounted, neither when invoked during boot nor shutdown/reboot. Signed-off-by: Torbjörn Svensson <azoff@svenskalinuxforeningen.se> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-21psplash: Avoid mount the psplash tmpfs twiceKevin Hao
The /etc/init.d/psplash.sh will be invoked both in boot and shutdown/reboot. And the psplash tmpfs will be mounted twice. This will trigger a bug in umount and let the system hang when shutdown/reboot. I already made a patch [1] to fix the issue in umount, but there is no reason for the psplash to do the twice mount. So also fix it. [Yocto 13461] [1] https://lore.kernel.org/util-linux/20190819083022.12289-1-kexin.hao@windriver.com/T/#u Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-07-20psplash: create psplash tmpfs mount directory in psplash-initStefan Agner
The psplash binary uses TMPDIR as directory to store the FIFO to communicate with the psplash tools. This directory can be in any location an init system determines to be suitable, psplash-init uses /mnt/ for it. Rather than creating the mount directory in the recipe, just create it in the init script itself. This allows other init scripts to use a different location without having an unnecessary .psplash directory in /mnt. Signed-off-by: Stefan Agner <stefan.agner@toradex.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-09-11psplash: Initialize psplash only if a framebuffer existsMark Hatle
psplash-init exits if there is no framebuffer device detected. This is done to avoid the following error message from occurring when booting up: "Error opening /dev/fb0: No such file or directory" Signed-off-by: Aws Ismail <aws.ismail@windriver.com> Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2010-08-27Major layout change to the packages directoryRichard Purdie
Having one monolithic packages directory makes it hard to find things and is generally overwhelming. This commit splits it into several logical sections roughly based on function, recipes.txt gives more information about the classifications used. The opportunity is also used to switch from "packages" to "recipes" as used in OpenEmbedded as the term "packages" can be confusing to people and has many different meanings. Not all recipes have been classified yet, this is just a first pass at separating things out. Some packages are moved to meta-extras as they're no longer actively used or maintained. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>