u-boot rk356х (rockchip repository)

[hamsterbacke]

This is somewhat diffent to the howto at https://pine64.org/documentation/Quartz6...ng_U-Boot/.
If I do it like the official documentation says it is not working. I have a model A.
I used idbloader.img for the "loader" partition.
I get following debug information when compiling u-boot with debugging on:

Code:

...
Bootdev 'mmc@fe2b0000.bootdev' part 4 method 'extflow
check - ret=0
  1  extlin  4  mmc@fe2b0000.bootdev.part /extlinux/extlinux.conf
** Booti 'mmc@fe2b0000.bootdev.part_4' with extlinux
Quartz64 Boot Menu
1:    Boot Arch Kernel
Enter choice: 1:    Boot Arch Kernel
Retrieving file: /Image
count = 128 * 128 start 0x10000, size 0x100000, name efi
FAT read(sect=2080), clust_size=8, read_size=8
count = 128 * 128 = 16384
start 0x10000, size 0x100000, name efi
FAT read(sect=2080), clu=8, read_size=8
Retrieving file: /initramfs-linux.img
count = 128 * 128 = 16384start 0x10000, size 0x100000, name efi
FAT read(sect=2080), clucount = 128 * 128 = 16384
start 0x10000, size 0x100000, name efi
FAT read(sect=2080), clust_size=8, read_size=8
append: earlycon=uart8250,mmio32,0xfe660000 console=ttyS2,1500000n8 root=LABEL=rootfs rw rootwaitrieving file: /dtbs/rockchip/rk3566-quartz64-a.dtb
count = 12884
start 0x10000, size 0x100000, name efi
FAT read(sect=2080), clust_size=8, read_size=8
FAT read(sect=138104), clust_size=8, read_size=8
FAT read(sect=476000), clust_size=8, read_size=8
FAT read(sect=619008), clust_size=8, read_size=8
FAT read(sect=626016), clust_size=8, read_size=8
FAT read(sect=635424), clust_size=8, read_size=8
FAT read(sect=643976), clust_size=8, read_size=8
count = 128 * 128 = 16384
start 0x10000, size 0x100000, name efi
FAT read(sect=2080), clud_size=8
FAT read(sect=138104), clust_size=8, read_size=8
FAT read(sect=476000), clust_size=8, read_size=8
FAT read(sect=619008), clust_size=8, read_size=8
FAT read(sect=626016), clust_size=8, read_size=8
FAT read(sect=635424), clust_size=8, read_size=8
FAT read(sect=643976), clustize=8
using booti
FIT check error -99
## Flattened Device Tree blob at 12000000
   Booting using the fdt blob atWorking FDT set to 12000000
   Loading Ramdisk to ec154000, end ecbffba1 ... OK
   Loading Device Tree to 00000000ece76000, end 00000000ece9 ... OK
Working FDT set to ece76000

Starting kernel ...

Sending event 6/(unknown) to spy 'efi_ddel'
Sending event 6/(unknown) to spy 'efi_disk del'
Sending eown) to spy 'efi_disk del'
io-dgs=4600, drv->flags=0, err=-129
syscon@fdc20000: When removing:, drv->flags=0, err=-129
Sending event 6/(unknown) to spy 'efi_disk del'
syscon@fdc60000: When removing: flags=4600, drv->flagrr=-129
Sending event 6/(unknow
                       clock-controller@fdd00000: When removing: flags=4600, drv->flag9
Sending event 6/(unknown) to g event 6/(unknown) to spy 'efi_disk del'
reset: When removing:, drv->flags=0, err=-129
clock-controller@fdd20000: When removing: flags=4600, drv->flags=0, err=-129
Sending event 6/(unknownpy 'efi_disk del'
Sending eventdisk del'
Sending event 6/(unknown) to spy 'efi_disk del'
DCDCremoving: flags=4600, drv->flagst 6/(unknown) to spy 'efi_disk del'
DCDC_REG2: When removing: fdrv->flags=0, err=-129
Sending event 6/(unknown) to spy 'efi_disk del'

When I use the u-boot from the documentation https://pine64.org/documentation/Quartz6...ing-u-boot
it works with the following output:

Code:

Fdt Ramdisk skip relocation
## Flattened Device Tree blob at 0x0a100000
   Booting using the fdt blob at 0x0a100000
  'reserved-memory' shmem@10f000: addr=10f000 size=100
   Using Device Tree in place at 000000000a100
can't found rockchip,drm-logo, use rockchip,fb-logo
WARNING: could not set reg FDT_ERR_BADOFFSET.
failed to reserve fb-loader-logo memory
Adding b000 (size: 0x08200000)
Adding bank: 0x09400000 - 0xf0000000 (size: 0xe6c00000)
Adding bank: 0x100000000 - 0x200000000 (size: 00000)
Total: 10011.903 ms

Starting kernel ...
...
and so on with systemd messages

Do I need to disable ramdisk relocation? It isn't working with the current u-boot git tree and the corresponding quartz64-a-rk3566_defconfig.
Just curious of what might has changed.