On 12/2/22 04:19, Fabio Estevam wrote:
Hi Heinrich,
On Tue, Nov 22, 2022 at 5:42 AM Oliver Graute oliver.graute@kococonnector.com wrote:
since commit c5ef2025579e91f132cd3cead8ebe8b4cd5dd2b6 its necessary to set CONFIG_EVENT for a successful boot of this board again
Signed-off-by: Oliver Graute oliver.graute@kococonnector.com CC: heinrich.schuchardt@canonical.com
configs/imx8qm_rom7720_a1_4G_defconfig | 1 + 1 file changed, 1 insertion(+)
diff --git a/configs/imx8qm_rom7720_a1_4G_defconfig b/configs/imx8qm_rom7720_a1_4G_defconfig index afec319640..002babeff2 100644 --- a/configs/imx8qm_rom7720_a1_4G_defconfig +++ b/configs/imx8qm_rom7720_a1_4G_defconfig @@ -90,6 +90,7 @@ CONFIG_DM_REGULATOR_FIXED=y CONFIG_DM_REGULATOR_GPIO=y CONFIG_SPL_DM_REGULATOR_GPIO=y CONFIG_DM_SERIAL=y +CONFIG_EVENT=y
Could you please take a look? What is the proper fix for this issue?
Thanks
Hello Simon,
in lots of places we have 'imply DM_EVENT' which of course has no effect if CONFIG_EVENT=n.
We always have CONFIG_DM=y. Why do we need separate symbols CONFIG_EVENT and CONFIG_DM_EVENT?
Can we drop CONFIG_DM_EVENT? This should resolve the problem booting boards with CONFIG_EFI_LOADER=n that Fabio reported.
Best regards
Heinrich