On Mon, Jul 01, 2019 at 10:22:46PM +0200, Heinrich Schuchardt wrote:
Hmm. Well, my main concern is that we *should* be ignoring whatever is in the DT when booting through UEFI (see Linux commit 500899c2cc3e3).
Could you try deleting the "memory" and "memory@10000000" nodes from the DT and see if that changes behaviour? (You probably want to delete one of them regardless, since they describe the same region :)
setenv bootargs console=$console earlyprintk load mmc 2:2 $fdt_addr_r dtb fdt addr $fdt_addr_r fdt rm /memory fdt rm /memory@10000000 load mmc 2:1 $kernel_addr_r EFI/debian/grubarm.efi bootefi $kernel_addr_r $fdt_addr_r
leads to the same result.
Well, it was a bit optimistic hoping it would work...
If that doesn't change anything, how far back would we be able to bisect and still be able to boot on this platform?
I do not know if it ever worked for this board. U-Boot v2019.01 fails too.
I was basically wondering if 500899c2cc3e3 would be likely to work on this board in any environment?
I have not seen the problem on 32bit Amlogic (OrangePi PC).
Is this a distro kernel? Is the behaviour the same on upstream?
I have used 4.19.55 upstream together with the Debian config file but with earlyprintk enabled.
Ah, that makes sense.
Best Regards,
Leif