On 7/26/2021 6:26 PM, ci_not...@linaro.org wrote:
Successfully identified regression in *linux* in CI configuration
tcwg_kernel/llvm-release-aarch64-next-allnoconfig. So far, this commit has
regressed CI configurations:
- tcwg_kernel/llvm-release-aarch64-next-allnoconfig
Culprit:
<cut>
commit 8633ef82f101c040427b57d4df7b706261420b94
Author: Javier Martinez Canillas <javi...@redhat.com>
Date: Fri Jun 25 15:13:59 2021 +0200
drivers/firmware: consolidate EFI framebuffer setup for all arches
The register_gop_device() function registers an "efi-framebuffer" platform
device to match against the efifb driver, to have an early framebuffer for
EFI platforms.
But there is already support to do exactly the same by the Generic System
Framebuffers (sysfb) driver. This used to be only for X86 but it has been
moved to drivers/firmware and could be reused by other architectures.
Also, besides supporting registering an "efi-framebuffer", this driver can
register a "simple-framebuffer" allowing to use the siple{fb,drm} drivers
on non-X86 EFI platforms. For example, on aarch64 these drivers can only
be used with DT and doesn't have code to register a "simple-frambuffer"
platform device when booting with EFI.
For these reasons, let's remove the register_gop_device() duplicated code
and instead move the platform specific logic that's there to sysfb driver.
Signed-off-by: Javier Martinez Canillas <javi...@redhat.com>
Acked-by: Borislav Petkov <b...@suse.de>
Acked-by: Daniel Vetter <daniel.vet...@ffwll.ch>
Signed-off-by: Thomas Zimmermann <tzimmerm...@suse.de>
Link:
https://patchwork.freedesktop.org/patch/msgid/20210625131359.1804394-1-javi...@redhat.com
</cut>
Results regressed to (for first_bad == 8633ef82f101c040427b57d4df7b706261420b94)
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_llvm:
-5
# build_abe qemu:
-2
# linux_n_obj:
600
# First few build errors in logs:
# 00:00:38 ld.lld: error: undefined symbol: screen_info
# 00:00:38 make: *** [vmlinux] Error 1
It is good to see these reports again :)
This was reported by Mark Brown today for linux-next and Javier pointed
out there is a pending patch already for this:
https://lore.kernel.org/r/20210726213600.4054-1-broo...@kernel.org/
Cheers,
Nathan
_______________________________________________
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain
