lid 8 byte aligned address) solves this issue.
Signed-off-by: Matthias Schoepfer
CC: Mateusz Kulikowski
---
include/configs/dragonboard410c.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/configs/dragonboard410c.h
b/include/configs/dragonboard410c.h
index 65149ad441..9362e9322c 100
ing it to a valid 8 byte aligned
address) solves this issue.
Signed-off-by: Matthias Schoepfer
CC: Mateusz Kulikowski
---
include/configs/dragonboard410c.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/configs/dragonboard410c.h
b/include/configs/dragonboard410c.h
index 65149ad441..9362e93
age creation?!
I wonder, whether just removing fdt_high is a valid solution...
Regards,
Matthias
On 1/6/20 3:20 PM, Tom Rini wrote:
On Mon, Jan 06, 2020 at 01:47:25PM +0100, Matthias Schoepfer wrote:
Hi!
I have had trouble booting a fitImage packed kernel for dragonboard410c,
which is an AR
Hi!
I have had trouble booting a fitImage packed kernel for dragonboard410c,
which is an ARM64 platform. After days and days of debugging, I found
that the fdt is 4-byte aligned. But within the linux kernel,
Documentation/arm64/booting.txt says, fdt must be 8 byte aligned.
If I change the
Hi!
We have a Dragonboard 410c. We chainload u-boot from little kernel (lk),
and from there the linux kernel obviously. All of it (not little kernel)
is build within yocto / Openembedded. It will generate a fitImage, that
we put into an ext4 partition, from there we bootm the stuff after
5 matches
Mail list logo