<aggi>
question: is it possible to launch an aarch32 linux kernel from an aarch64 uboot (bl31 atf etc.)??; had not seen anything yet from earlyprintk, nothing..
camus1 has joined #u-boot
camus has quit [Ping timeout: 240 seconds]
camus1 is now known as camus
persmule has quit [Ping timeout: 276 seconds]
persmule has joined #u-boot
samekh_ has joined #u-boot
samekh has quit [Ping timeout: 250 seconds]
sdfgsdfg has joined #u-boot
mmu_man has quit [Ping timeout: 240 seconds]
v0|d has quit [Remote host closed the connection]
thopiekar has quit [Ping timeout: 240 seconds]
thopiekar has joined #u-boot
alchemist_ has joined #u-boot
alchemist has quit [Ping timeout: 256 seconds]
camus has quit [Read error: Connection reset by peer]
camus1 has joined #u-boot
camus1 is now known as camus
taliho has joined #u-boot
camus has quit [Ping timeout: 240 seconds]
camus has joined #u-boot
vagrantc has quit [Quit: leaving]
flyback has quit [Remote host closed the connection]
<rdo>
I read: If offset is positive (the usual case), it is treated as relative to the start of the MMC partition.
<rdo>
CONFIG_SYS_MMC_ENV_PART=0 .... but what is partition zero?
<rdo>
Is that the /dev/mmcblk1 itself?
<rdo>
There is no /dev/mmcblk1p0, it starts with /dev/mmcblk1p1
sdfgsdfg has quit [Quit: ZzzZ]
<rdo>
So the question comes down to: where does u-boot read/write the environment with my u-boot config: https://paste.debian.net/1225366/
v0|d has joined #u-boot
<marex>
rdo: the env magic is at offset 0x1600 in the hexdump
persmule has joined #u-boot
camus has joined #u-boot
camus has quit [Ping timeout: 250 seconds]
<rdo>
Is there a way in u-boot to dump the address of the env? I assume there is a base address somewhere which I am missing.
<rdo>
In the config I see CONFIG_SYS_TEXT_BASE=0x17800000 (376 MB) but that seems to big for me.
<marex>
rdo: TEXT_BASE is the link address of U-Boot (where it starts in DRAM, before relocation)
<marex>
the ENV_OFFSET is just a macro, it gets inlined into the code by the compiler, it isn't printed anywhere afterward
<marex>
could it be your env needs to be in a partition ?
<marex>
mmcblk1p1 or so ?
<marex>
try running fdisk -l /dev/mmcblk1 and see if that 0x1600 offset is by any chance the offset of first partition or so (remember , 0x1600 is in BYTES, fdisk might print the offsets in 512 B sectors)