openwrt/target/linux/ipq40xx
Robert Marko f1c80445bd ipq40xx: meraki: define DTB load address
It seems that the Meraki bootloader does not respect the kernel ARM booting
specification[1] that requires that address where DTB is located needs to
be 64-bit aligned and often places the DTB on a non 64-bit aligned address
and then kernel fails to find the DTB magic and fails to boot.
Even worse, there is no prints until early printk is enabled and then its
visible that kernel is trying to find the ATAG-s as DTB was not found or
is invalid.

Unifi 6 devices had the same issue and it can be solved by passing the
load adress as part of the FIT image.
It seems that the vendor was aware of the issue and is always relocating
the DTB to 0x89000000, so lets just do the same.

Now that booting is reliable, reenable default images for the Meraki MR33
and MR74 devices.

Reviewed-by: Lech Perczak lech.perczak@gmail.com
Signed-off-by: Robert Marko <robimarko@gmail.com>
2023-08-14 19:29:25 +02:00
..
base-files ipq40xx: add support for Teltonika RUTX50 2023-07-26 01:17:08 +02:00
chromium ipq40xx: cut ath10k board file for mikrotik subtarget 2022-05-27 14:15:09 +02:00
files ipq4019: fix support for AVM FRITZ!Repeater 3000 2023-07-26 12:26:45 +02:00
generic ipq40xx: cut ath10k board file for mikrotik subtarget 2022-05-27 14:15:09 +02:00
image ipq40xx: meraki: define DTB load address 2023-08-14 19:29:25 +02:00
mikrotik ipq40xx: cut ath10k board file for mikrotik subtarget 2022-05-27 14:15:09 +02:00
patches-5.15 kernel: bump 5.15 to 5.15.123 2023-07-30 18:02:47 +02:00
config-5.15 ipq40xx: Enable gpio-restart in kernel configuration 2023-06-25 15:53:03 +02:00
Makefile treewide: replace wpad-basic-wolfssl default 2023-02-04 02:35:03 +01:00