linux/poky.git/meta/recipes-core/psplash, branch master

The poky repository master branch is no longer being updated.

2025-11-07T13:31:53+00:00

You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie

psplash: Do not mount PSPLASH_FIFO_DIR if the env variable is empty

2025-08-25T16:47:20+00:00

The script file psplash.sh tries to mount the PSPLASH_FIFO_DIR variable. If the variable is empty, the mountpoint command returns a usage text (busybox mountpoint here, util-linux mountpoint behaves the same): BusyBox v1.37.0 () multi-call binary. Usage: mountpoint [-q] { [-dn] DIR | -x DEVICE } :~# BusyBox v1.37.0 () multi-call binary The return code with this console output is 0 and the mount command in the if statement is executed. Then this mount also fails with an empty mountpoint argument. The source code of psplash respects an empty PSPLASH_FIFO_DIR variable (see psplash.c) and makes a fallback to "/run". So the psplash.sh script should also respect the empty var. Try to mount the PSPLASH_FIFO_DIR only if the variable is not empty. (From OE-Core rev: 85a5e562c5969c407a222966ccb3170cb41fed2f) Signed-off-by: Falk Bauer Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

meta: remove consecutive blank lines

2025-06-20T11:07:27+00:00

Some of them were introduced by mass-removal of S = WORKDIR/git assignments; rather than try to fix up (or redo) just these, I've run this sed command over the whole tree: sed -i -z -E 's/([ \t\f\v\r]*\n){3,}/\n\n/g' `find . -name *.bb -o -name *.inc` The rationale is that more than one empty line is wasting vertical screen space, and does nothing for readability. (From OE-Core rev: cedc4ff7c9bcfb22a20e43e47f9759f4007a4f1a) Signed-off-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

meta: remove S in recipes that fetch from git via setting BB_GIT_DEFAULT_DESTSUFFIX

2025-06-20T11:07:26+00:00

Removing all the S = ${WORKDIR}/git assignments works because BB_GIT_DEFAULT_DESTSUFFIX is set to match S from bitbake.conf (which itself is set to match typical tarball releases). A few recipes are setting S to a sub-directory of the git tree and need to be adjusted accordingly. bzip2 recipe is fetching a tarball and separately cloning tests; adjust the recipe to put the latter into 'bzip2-tests', instead of 'git'. devupstream.bbclass no longer needs to rewrite S, and is adjusted accordingly. Adjust scripts/lib/recipetool/append.py to not hardcode 'git' as unpack destination. Adjust kernel-yocto.bbclass to use the git unpack variable instead of hardcoding 'git' (there's also removal of repetition of string constants and a correction of workdir/unpackdir mismatch in one of the if-else branches). Ensure build-appliance-image recipe does not use 'git' as checkout directory for poky repo, but rather explicitly name it 'poky'. Ensure reproducible.py code that looks for git repositories does not hardcode 'git' but uses the destination set by BB_GIT_DEFAULT_DESTSUFFIX. Ensure recipetool does not write out unneeded S settings into newly created recipes that fetch from git. Adjust selftest to not hardcode 'git' as unpack directory. (From OE-Core rev: f80c07019ddadaf9c5fb890faabfda7920ecd15e) Signed-off-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

psplash: update to latest rev

2025-05-27T08:01:16+00:00

* 53ae74a3 configure.ac: fix autoconf code for img_fullscreen * ec1ed353 configure.ac: standardize default-enabled options (From OE-Core rev: 1a91da3acc442cece76e45d6d81f97326764984a) Signed-off-by: Yi Zhao Signed-off-by: Richard Purdie

psplash: Fix build with GCC 15

2025-03-20T11:29:03+00:00

Pull in upstream changes for fix the build with gcc 15 and README tweaks. (From OE-Core rev: 0ba624f30d482c0c7d86202d46abdab9d148c9b0) Signed-off-by: Richard Purdie

psplash: ignore startup errors in psplash-systemd.service

2025-02-28T07:49:18+00:00

psplash-systemd.service depends on FIFO created by psplash-start@fb0.service. This FIFO can be removed due to signals or /dev/fb0 related errors when psplash-start@fb0.service exits. This exit can happen when psplash-systemd.service is being started. Thus ignore all errors in psplash-systemd.service startup. There are too many ways things can go wrong and all of them leave open race conditions unless a single process handles all of the psplash usecases including progress bar updates. (From OE-Core rev: 580ae81e102bf999cb89f05430c737210253d90a) Signed-off-by: Mikko Rapeli Signed-off-by: Richard Purdie

psplash: fix typo in psplash-systemd.service

2025-02-21T13:08:44+00:00

systemd ignores the typo and continues but startup fails later due to missing fifo file. Fixes: systemd[1]: /usr/lib/systemd/system/psplash-systemd.service:8: Unknown key 'ConditionFileExists' in section [Unit], ignoring. (From OE-Core rev: c7215ad8599a4b792d7edefb46861c94a7ba79b3) Signed-off-by: Mikko Rapeli Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

psplash: update to latest rev

2025-02-18T11:56:04+00:00

* 5a32cf6 psplash.c: fix crash from length becoming negative (From OE-Core rev: 1845f785359a689add866881286fdac38753e5bb) Signed-off-by: Yi Zhao Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

psplash: start via udev if framebuffer device detected

2025-02-18T11:56:04+00:00

psplash-start.service expected to find /dev/fb0 and failed if device was not found. This failure breaks systemd oeqa runtime test with "runqemu nographic". Starting psplash based on detected framebuffer device fixes systemd boot status and systemd oeqa runtime tests for qemu boots with and without graphics support. Note that psplash-systemd.service still depends on /dev/fb0 so startup with multiple framebuffer devices may not work correctly. I don't have devices with multiple framebuffer devices to test with. On qemu machine with graphics, psplash displays yocto logo correctly and boot progress bar as well. Once boot completes to systemd "running" state, the logo is replaced by login prompt. On qemu machine without graphics, boot completes without psplash or failures and login over serial console works normally. Tested with genericarm64 machine poky-altcfg distro and core-image-base image on qemu. AMD kv260 tested as well but graphics stack is not yet working there so boot is similar to qemu without graphics. (From OE-Core rev: 3820f6f342c2309ba7d51d3c08b3a951c2c17781) Signed-off-by: Mikko Rapeli Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie