Linux UEFI Validation Project v2.4-rc2 release
by Megha Dey
Hello,
This is to announce the release of LUV v2.4-rc2. It includes the usual
updates to yocto, meta-oe, various test suites kernel version and bug
fixes.
This release comes about 7 months after our last release. We have been
working on shifting LUV from being a fork of the yocto project to
maintaining a meta-luv layer only git repository. We will have a
separate git which will pull all the other required layers from the
open-embedded project to build the final LUV image. This would make
maintaining the project easier, make the project more open for others
to contribute and ensure that the project builds on ARM platforms. We
have been in the process of getting this project approved internally
and it seems to be taking quite a while.
=== Updates:
1. updated changes from the poky and meta-openembedded repos. (New
branch warrior)
2. updated the Linux kernel version to 5.1
3. updated FWTS to v19.06.00
4. updated chipsec to v1.3.7
5. The LUV project was successfully compiled on ThunderX Workstation
natively.
=== Bug Fixes
1. Fixed all the issues which arose as a result of the above updates.
2. If reboots-tests are enabled, an extra directory was created in the
results folder.
3. On certain systems, systemd failed to use ttyS0 as Standard Output
=== Features
1. Update script to modify LUV parameters
2. Splash and frame buffer support was added to the ARM LUV image. The
graphics testing was done on a ThunderX2 WorkStation
== Binary images for x86:
The release images for x86 (disk and network) are available at
https://download.01.org/linux-uefi-validation/v2.4/
=== Known issues
1. Bits is not running on 32 bit systems. Looks like this has started
after we updated grub from v2.0 to v2.02.
2. Netconsole in bits does not work if the listener is on a different
subnet compared to the host.
3. When running netconsole, we only see logs from chipsec and ndctl
test suites
=== Short log:
Many thanks to all the contributors of this release. This is how the
short log looks:
Megha Dey (21):
Merge branch warrior of git://git.yoctoproject.org/poky
Merge branch warrior of git://git.openembedded.org/meta-
openembedded
meta-luv: update LAYERSERIES_COMPAT_luv variable
qemu: Update to 3.1.0
systemd: Update to v241
ndctl: Update to v63
plymouth: Update to 0.9.4
plymouth: Do not hardcode number of test-suites
chipsec: Bump to version v1.3.7
fwts: Update fwts to v19.06.00
linux-luv: Bump kernel to v5.1
linux-luv: Remove unused patch
linux-libc-headers: Bump linux-libc-headers to v5.1
luv: increase the maximum size of the initramfs
luv-test: Do not create extra results directory
meta-luv/utils/: Update script to modify LUV parameters
luv-test: Do not use tty as standard output for x86
meta-luv/README: Update README
pstore-test: Ensure do_patch executes after linux-luv:do_patch
Plymouth: Revert commit that uses device timeout
LUV v2.4-rc2
Naresh Bhat (4):
aarch64: Enable FB and bootup logo
luv-image:Add splash and nomodeset to cmdline base
luv-image: Move crash kexec post notifiers to CMDLINE_BASE
efivarfs-test: Ensure the kernel source available
Thanks,
Megha
3 years, 1 month
[Results] Inspiron 7572 - BIOS 1.2.1, luv v2.4-rc2
by Mateus Rodrigues Costa
Hello, LUV mailing list.
I noticed on Dell's website that a bios update recently got released and I
installed it, today I decided to test it with LUV. Then I also noticed a
LUV update, so here I am testing it with the latest rc.
Info about the laptop:
Dell Inspiron 5420
Intel Core i5-8250U
8 GB RAM
Bios Version 1.2.1 (Secure Boot disabled, UEFI-only mode selected)
I used the v2.4-rc2 x86_64 gpt image and, differently from a previous
attempt with a previous version of luv, this time all the tests worked
instead of just everything freezing.
It also seems this laptop will still get bios updates for a while, so I
hope sending the results here can help Dell correct any issue that might
cause me problems when running Linux. (An important note is that this
laptop shipped with Ubuntu, not Windows, and I just switched it for Arch
Linux).
The BIOS is available here:
https://www.dell.com/support/home/br/pt/brbsdt1/drivers/driversdetails?dr...
And the results zip is attached to this message.
I might also re-do the luv tests on my old Inspiron 5420 too, since it is
lying around not doing much. (It also doesn't receives bios updates anymore
afaik)
PS: Also, sorry for not following up previous messages in this mailing
list. In all previous attempts to reply to people I used "Reply", but it
seems this specific mailing list needed me to use "Reply All" for whatever
reason.
Thanks for your time,
Mateus Rodrigues Costa
3 years, 2 months
[PATCH] efivarfs-test: Ensure the kernel source available
by Naresh Bhat
The efivarfs-test is looking for kernel-source COPYING file.
So the changes in this patch will make sure that the kernel
source code is downloaded and available before executing the
efivarfs test do_populate_lic function.
Error logs:
build$ bitbake luv-live-image
...
..........
WARNING: efivarfs-test-1.0-r0 do_populate_lic: Could not copy license file /luv-live-image/luv-yocto/build/tmp/work-shared/qemuarm64/kernel-source/COPYING to luv-live-image/luv-yocto/build/tmp/work/aarch64-oe-linux/efivarfs-test/1.0-r0/license-destdir/efivarfs-test/COPYING: [Errno 2] No such file or directory: 'luv-live-image/luv-yocto/build/tmp/work-shared/qemuarm64/kernel-source/COPYING'
ERROR: efivarfs-test-1.0-r0 do_populate_lic: QA Issue: efivarfs-test: LIC_FILES_CHKSUM points to an invalid file: luv-live-image/luv-yocto/build/tmp/work-shared/qemuarm64/kernel-source/COPYING [license-checksum]
ERROR: efivarfs-test-1.0-r0 do_populate_lic: Fatal QA errors found, failing task.
ERROR: efivarfs-test-1.0-r0 do_populate_lic:
ERROR: efivarfs-test-1.0-r0 do_populate_lic: Function failed: populate_lic_qa_checksum
ERROR: Logfile of failure stored in: luv-live-image/luv-yocto/build/tmp/work/aarch64-oe-linux/efivarfs-test/1.0-r0/temp/log.do_populate_lic.12125
ERROR: Task (luv-live-image/luv-yocto/meta-luv/recipes-core/efivarfs/efivarfs-test.bb:do_populate_lic) failed with exit code '1'
NOTE: Tasks Summary: Attempted 914 tasks of which 0 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
luv-live-image/luv-yocto/meta-luv/recipes-core/efivarfs/efivarfs-test.bb:do_populate_lic
Summary: There were 2 WARNING messages shown.
Summary: There were 4 ERROR messages shown, returning a non-zero exit code.
luv-live-image/luv-yocto/build$
Changes V0->V1:
The changes made from do_patch[depends] += "linux-luv:do_patch" to
do_populate_lic[depends] += "virtual/kernel:do_shared_workdir" as
suggested by Ricardo Neri on LUV ML.
Suggested-by: Ricardo Neri <ricardo.neri(a)intel.com>
Signed-off-by: Naresh Bhat <naresh.bhat(a)linaro.org>
---
meta-luv/recipes-core/efivarfs/efivarfs-test.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-luv/recipes-core/efivarfs/efivarfs-test.bb b/meta-luv/recipes-core/efivarfs/efivarfs-test.bb
index fd1fab1828..1d0253ba4d 100644
--- a/meta-luv/recipes-core/efivarfs/efivarfs-test.bb
+++ b/meta-luv/recipes-core/efivarfs/efivarfs-test.bb
@@ -55,6 +55,8 @@ do_install() {
install -m 0755 ${WORKDIR}/efivarfs ${D}${bindir}
}
+do_populate_lic[depends] += "virtual/kernel:do_shared_workdir"
+
LUV_TEST_LOG_PARSER="luv-parser-efivarfs"
LUV_TEST_JSON="efivarfs.json"
LUV_TEST="efivarfs"
--
2.17.1
3 years, 2 months
[PATCH V2] pstore-test: Ensure do_patch executes after linux-luv:do_patch
by Megha Dey
We introduced a placeholder REBOOT_DIR in the pstore selftests as
part of commit 251961 "linux-yocto-efi-test: pstore selftest reboot
flag" which ultimately should be replaced by the location of the
directory which survives a reboot in case we opt for the pstore
reboot tests.
Thus, we must ensure that the kernel source code is downloaded, the
placeholder is added and only then update the placeholder with the
actual value from the pstore-test.bb recipe. It so happens that this
dependency is not strict, hence we sometimes observe that the
pstore-test:do_patch runs earlier than the kernel's do_patch task
and thus placeholder is not replaced with actual contents, and the
pstore -tests do not execute as expected.
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
meta-luv/recipes-core/pstore-test/pstore-test.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-luv/recipes-core/pstore-test/pstore-test.bb b/meta-luv/recipes-core/pstore-test/pstore-test.bb
index 5f55553..efd0002 100644
--- a/meta-luv/recipes-core/pstore-test/pstore-test.bb
+++ b/meta-luv/recipes-core/pstore-test/pstore-test.bb
@@ -33,6 +33,8 @@ do_patch_append() {
bb.build.exec_func('patch', d)
}
+do_patch[depends] += "virtual/kernel:do_patch"
+
do_configure_prepend() {
# We need to ensure the --sysroot option in CC is preserved
if [ -e "${STAGING_KERNEL_DIR}/tools/testing/selftests/pstore/Makefile" ]; then
--
2.7.4
3 years, 2 months
FWTS 19.07.00 is released
by Alex Hung
It is available from:
Tar: http://fwts.ubuntu.com/release/fwts-V19.07.00.tar.gz
PPA: https://launchpad.net/~firmware-testing-team/+archive/ubuntu/ppa-fwts-stable
Release notes: https://wiki.ubuntu.com/FirmwareTestSuite/ReleaseNotes/19.07.00
= New Features =
* cpu/msr: add 3 more CPU IDs for IA32_silvermont_MSRs
* cpu/msr: check SGX & LMCE in IA32_FEATURE_CONTROL (3ah)
* cpu/msr: move TSC_ADJUST (3bh) to IA32_MSRs
* cpu/msr: add SMM_MONITOR_CTL (9bh) to IA32_MSRs
* cpu/msr: add MC*_CTL2 MSR registers
* cpu/msr: add VMX_VMFUNC MSR register
* cpu/msr: add MISC_ENABLE MSR to IA32_atom_MSRs
* cpu/msr: add MSR_PMG_IO_CAPTURE_BASE to IA32_silvermont_MSRs
* cpu/msr: add MSR_FEATURE_CONFIG to IA32_silvermont_MSRs
* cpu/msr: add MSR_TEMPERATURE_TARGET to IA32_silvermont_MSRs
* cpu/msr: add MSR_BBL_CR_CTL3 to IA32_silvermont_MSRs
* ACPICA: Update to version 20190703
= Fixed Bugs =
* cpu/msr: update MTRRCAP MSR register
* cpu/msr: update PAT MSR PA0[2:0]
* cpu/msr: update fields for MTRR_DEF_TYPE MSR
* cpu/msr: remove same MSR registers in IA32_MSRs
* cpu/msr: update THERM_INTERRUPT MSR masks
* cpu/msr: update MISC_ENABLE to IA32_silvermont_MSRs
* cpu/msr: remove MSR for Error-Reporting Register Banks
* cpu/msr: remove EBL_CR_POWERON (2ah) from IA32_MSRs
* cpu/msr: add document info the cpu_msr_map table
* cpu/msr: skip read-only MCG_CAP MSR
* Move libfwtsacpica and libfwtsiasl into their own directories
* Makefiles: hard code paths to workaround autotool bug
* lib: fwts_framework: fix memory leak on fw->fdt
* fwts: opal: fix memory leak of 'buf'.
* acpi: method: skip over bad method_handle and failed message type
* acpi: method: add null pointer sanity checks on resource
* acpi: method: add more null pointer sanity checks on resource
* acpi: s3/s4: initialize error to zero
* lib: fwts_pipeio: zero pollfds to squish a static analysis warning
* dsddump: fix segfault on type ACPI_TYPE_LOCAL_REFERENCE
= Detail Changelog =
To check /usr/share/doc/fwts/changelog.Debian.gz or
fwts_19.07.00.00-0ubuntu1.debian.tar.gz from
https://launchpad.net/ubuntu/+source/fwts
3 years, 2 months
[PATCH] efivarfs-test: Ensure do_patch executes after linux-luv:do_patch
by Naresh Bhat
The efivarfs-test:do_patch executes earlier than the do_patch kernel's
task. We must make sure that the kernel source code is downloaded and
available before executing the efivarfs test do_patch function.
Signed-off-by: Naresh Bhat <naresh.bhat(a)linaro.org>
---
meta-luv/recipes-core/efivarfs/efivarfs-test.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta-luv/recipes-core/efivarfs/efivarfs-test.bb b/meta-luv/recipes-core/efivarfs/efivarfs-test.bb
index fd1fab1828..2f1851de7d 100644
--- a/meta-luv/recipes-core/efivarfs/efivarfs-test.bb
+++ b/meta-luv/recipes-core/efivarfs/efivarfs-test.bb
@@ -54,6 +54,7 @@ do_install() {
install -d ${D}${bindir}
install -m 0755 ${WORKDIR}/efivarfs ${D}${bindir}
}
+do_patch[depends] += "linux-luv:do_patch"
LUV_TEST_LOG_PARSER="luv-parser-efivarfs"
LUV_TEST_JSON="efivarfs.json"
--
2.17.1
3 years, 2 months
[PATCH] Plymouth: Revert commit that uses device timeout
by Megha Dey
After updating to plymouth 0.9.4, we see that if we execute the reboot
tests (and reboot through kexec), the splash screen does not come up.
All we see is the penguins (indicating Linux boot) and a blinking
cursor. On doing a git bisect, commit 7e37d58 "device-manager: use
device timeout instead of udev coldplug monitor" is the offending patch.
For now revert this patch (not a clean revert), as we are not sure why
this patch causes this behavior.
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
...th-Revert-commit-that-uses-device-timeout.patch | 236 +++++++++++++++++++++
.../recipes-core/plymouth/plymouth_0.9.4.bbappend | 1 +
2 files changed, 237 insertions(+)
create mode 100644 meta-luv/recipes-core/plymouth/files/0001-Plymouth-Revert-commit-that-uses-device-timeout.patch
diff --git a/meta-luv/recipes-core/plymouth/files/0001-Plymouth-Revert-commit-that-uses-device-timeout.patch b/meta-luv/recipes-core/plymouth/files/0001-Plymouth-Revert-commit-that-uses-device-timeout.patch
new file mode 100644
index 0000000..e474773
--- /dev/null
+++ b/meta-luv/recipes-core/plymouth/files/0001-Plymouth-Revert-commit-that-uses-device-timeout.patch
@@ -0,0 +1,236 @@
+From 79c17fe6b8dd9564a13b0283bfe1a0fe8d0a19e1 Mon Sep 17 00:00:00 2001
+From: Megha Dey <megha.dey(a)linux.intel.com>
+Date: Fri, 19 Jul 2019 11:16:26 -0700
+Subject: [PATCH] Plymouth: Revert commit that uses device timeout
+
+After updating to plymouth 0.9.4, we see that if we execute the reboot
+tests (and reboot through kexec), the splash screen does not come up.
+All we see is the penguins (indicating Linux boot) and a blinking cursor.
+On doing a git bisect, commit 7e37d58 "device-manager: use device timeout
+instead of udev coldplug monitor" is the offending patch.
+
+For now revert this patch (not a clean revert), as we are not sure why
+this patch causes this behavior.
+
+Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
+---
+ src/libply-splash-core/ply-device-manager.c | 80 ++++++++++++++++++++++++-----
+ src/libply-splash-core/ply-device-manager.h | 1 -
+ src/main.c | 19 +------
+ 3 files changed, 67 insertions(+), 33 deletions(-)
+
+diff --git a/src/libply-splash-core/ply-device-manager.c b/src/libply-splash-core/ply-device-manager.c
+index 55248ac..d1b6f8e 100644
+--- a/src/libply-splash-core/ply-device-manager.c
++++ b/src/libply-splash-core/ply-device-manager.c
+@@ -62,6 +62,9 @@ struct _ply_device_manager
+ ply_list_t *text_displays;
+ ply_list_t *pixel_displays;
+ struct udev *udev_context;
++ struct udev_queue *udev_queue;
++ int udev_queue_fd;
++ ply_fd_watch_t *udev_queue_fd_watch;
+ struct udev_monitor *udev_monitor;
+ ply_fd_watch_t *fd_watch;
+
+@@ -353,16 +356,18 @@ on_udev_event (ply_device_manager_t *manager)
+
+ if (strcmp (action, "add") == 0) {
+ const char *subsystem;
++ bool coldplug_complete = manager->udev_queue_fd_watch == NULL;
+
+ subsystem = udev_device_get_subsystem (device);
+
+- if (strcmp (subsystem, SUBSYSTEM_DRM) == 0) {
+- if (manager->local_console_managed && manager->local_console_is_text)
++ if (strcmp (subsystem, SUBSYSTEM_DRM) == 0 ||
++ coldplug_complete) {
++ if (coldplug_complete && manager->local_console_managed && manager->local_console_is_text)
+ ply_trace ("ignoring since we're already using text splash for local console");
+ else
+ create_devices_for_udev_device (manager, device);
+ } else {
+- ply_trace ("ignoring since we only handle subsystem %s devices after timeout", subsystem);
++ ply_trace ("ignoring since we only handle subsystem %s devices after coldplug completes", subsystem);
+ }
+ } else if (strcmp (action, "remove") == 0) {
+ free_devices_for_udev_device (manager, device);
+@@ -524,11 +529,6 @@ ply_device_manager_free (ply_device_manager_t *manager)
+ if (manager == NULL)
+ return;
+
+- ply_event_loop_stop_watching_for_exit (manager->loop,
+- (ply_event_loop_exit_handler_t)
+- detach_from_event_loop,
+- manager);
+-
+ free_terminals (manager);
+ ply_hashtable_free (manager->terminals);
+
+@@ -827,7 +827,7 @@ create_devices_from_udev (ply_device_manager_t *manager)
+ return;
+ }
+
+- ply_trace ("Timeout elapsed, looking for devices from udev");
++ ply_trace ("Looking for devices from udev");
+
+ found_drm_device = create_devices_for_subsystem (manager, SUBSYSTEM_DRM);
+ found_fb_device = create_devices_for_subsystem (manager, SUBSYSTEM_FRAME_BUFFER);
+@@ -849,9 +849,64 @@ create_fallback_devices (ply_device_manager_t *manager)
+ PLY_RENDERER_TYPE_AUTO);
+ }
+
++static void
++on_udev_queue_changed (ply_device_manager_t *manager)
++{
++ if (!udev_queue_get_queue_is_empty (manager->udev_queue))
++ return;
++
++ ply_trace ("udev coldplug complete");
++ ply_event_loop_stop_watching_fd (manager->loop, manager->udev_queue_fd_watch);
++ manager->udev_queue_fd_watch = NULL;
++ udev_queue_unref (manager->udev_queue);
++
++ close (manager->udev_queue_fd);
++ manager->udev_queue_fd = -1;
++
++ manager->udev_queue = NULL;
++
++ create_devices_from_udev (manager);
++}
++
++static void
++watch_for_coldplug_completion (ply_device_manager_t *manager)
++{
++ int fd;
++ int result;
++
++ manager->udev_queue = udev_queue_new (manager->udev_context);
++
++ if (udev_queue_get_queue_is_empty (manager->udev_queue)) {
++ ply_trace ("udev coldplug completed already ");
++ create_devices_from_udev (manager);
++ return;
++ }
++
++ fd = inotify_init1 (IN_CLOEXEC);
++ result = inotify_add_watch (fd, "/run/udev", IN_MOVED_TO| IN_DELETE);
++
++ if (result < 0) {
++ ply_trace ("could not watch for udev to show up: %m");
++ close (fd);
++
++ create_fallback_devices (manager);
++ return;
++ }
++
++ manager->udev_queue_fd = fd;
++
++ manager->udev_queue_fd_watch = ply_event_loop_watch_fd (manager->loop,
++ fd,
++ PLY_EVENT_LOOP_FD_STATUS_HAS_DATA,
++ (ply_event_handler_t)
++ on_udev_queue_changed,
++ NULL,
++ manager);
++}
++
++
+ void
+ ply_device_manager_watch_devices (ply_device_manager_t *manager,
+- double device_timeout,
+ ply_keyboard_added_handler_t keyboard_added_handler,
+ ply_keyboard_removed_handler_t keyboard_removed_handler,
+ ply_pixel_display_added_handler_t pixel_display_added_handler,
+@@ -892,10 +947,7 @@ ply_device_manager_watch_devices (ply_device_manager_t *manager,
+ #ifdef HAVE_UDEV
+ watch_for_udev_events (manager);
+ create_devices_for_subsystem (manager, SUBSYSTEM_DRM);
+- ply_event_loop_watch_for_timeout (manager->loop,
+- device_timeout,
+- (ply_event_loop_timeout_handler_t)
+- create_devices_from_udev, manager);
++ watch_for_coldplug_completion (manager);
+ #endif
+ }
+
+diff --git a/src/libply-splash-core/ply-device-manager.h b/src/libply-splash-core/ply-device-manager.h
+index 389b636..f0c72d3 100644
+--- a/src/libply-splash-core/ply-device-manager.h
++++ b/src/libply-splash-core/ply-device-manager.h
+@@ -47,7 +47,6 @@ typedef void (* ply_text_display_removed_handler_t) (void *, ply_text_display_t
+ ply_device_manager_t *ply_device_manager_new (const char *default_tty,
+ ply_device_manager_flags_t flags);
+ void ply_device_manager_watch_devices (ply_device_manager_t *manager,
+- double device_timeout,
+ ply_keyboard_added_handler_t keyboard_added_handler,
+ ply_keyboard_removed_handler_t keyboard_removed_handler,
+ ply_pixel_display_added_handler_t pixel_display_added_handler,
+diff --git a/src/main.c b/src/main.c
+index ddc1883..58ca7bb 100644
+--- a/src/main.c
++++ b/src/main.c
+@@ -102,7 +102,6 @@ typedef struct
+
+ double start_time;
+ double splash_delay;
+- double device_timeout;
+
+ uint32_t no_boot_log : 1;
+ uint32_t showing_details : 1;
+@@ -288,6 +287,7 @@ load_settings (state_t *state,
+ char **theme_path)
+ {
+ ply_key_file_t *key_file = NULL;
++ const char *delay_string;
+ bool settings_loaded = false;
+ char *scale_string = NULL;
+ char *splash_string = NULL;
+@@ -316,8 +316,6 @@ load_settings (state_t *state,
+ }
+
+ if (isnan (state->splash_delay)) {
+- char *delay_string;
+-
+ delay_string = ply_key_file_get_value (key_file, "Daemon", "ShowDelay");
+
+ if (delay_string != NULL) {
+@@ -327,19 +325,6 @@ load_settings (state_t *state,
+ }
+ }
+
+- if (isnan (state->device_timeout)) {
+- char *timeout_string;
+-
+- timeout_string = ply_key_file_get_value (key_file, "Daemon", "DeviceTimeout");
+-
+- if (timeout_string != NULL) {
+- state->device_timeout = atof (timeout_string);
+- ply_trace ("Device timeout is set to %lf", state->device_timeout);
+-
+- free (timeout_string);
+- }
+- }
+-
+ scale_string = ply_key_file_get_value (key_file, "Daemon", "DeviceScale");
+
+ if (scale_string != NULL) {
+@@ -1100,7 +1085,6 @@ load_devices (state_t *state,
+ state->local_console_terminal = ply_device_manager_get_default_terminal (state->device_manager);
+
+ ply_device_manager_watch_devices (state->device_manager,
+- state->device_timeout,
+ (ply_keyboard_added_handler_t)
+ on_keyboard_added,
+ (ply_keyboard_removed_handler_t)
+@@ -2268,7 +2252,6 @@ main (int argc,
+
+ state.progress = ply_progress_new ();
+ state.splash_delay = NAN;
+- state.device_timeout = NAN;
+
+ ply_progress_load_cache (state.progress,
+ get_cache_file_for_mode (state.mode));
+--
+2.7.4
+
diff --git a/meta-luv/recipes-core/plymouth/plymouth_0.9.4.bbappend b/meta-luv/recipes-core/plymouth/plymouth_0.9.4.bbappend
index 57441ff..c27d9c2 100644
--- a/meta-luv/recipes-core/plymouth/plymouth_0.9.4.bbappend
+++ b/meta-luv/recipes-core/plymouth/plymouth_0.9.4.bbappend
@@ -7,6 +7,7 @@ SRC_URI+= "file://0001-plymouth-Add-the-retain-splash-option.patch \
file://0001-plymouth-modify-the-script-theme.patch \
file://0001-plymouth-Prevent-overwriting-of-messages.patch \
file://0001-plymouth-Do-not-hardcode-number-of-test-suites.patch \
+ file://0001-Plymouth-Revert-commit-that-uses-device-timeout.patch \
${SPLASH_IMAGES}"
SPLASH_IMAGES = "file://luv-splash.png;outsuffix=default"
--
2.7.4
3 years, 2 months