diff options
| author | Mattijs Korpershoek <mkorpershoek@baylibre.com> | 2024-10-03 14:42:39 +0200 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2024-10-03 11:30:25 -0600 |
| commit | 1b1ffda4207125c5bc618d4b0ca718b52cf7a4c0 (patch) | |
| tree | a59aa2ab41f11f329dfff2e2130ce3cc09c30c9f /board | |
| parent | 0ec0207fe07356bddb10db717e21c261bebfb989 (diff) | |
| download | u-boot-1b1ffda4207125c5bc618d4b0ca718b52cf7a4c0.tar.gz u-boot-1b1ffda4207125c5bc618d4b0ca718b52cf7a4c0.tar.bz2 u-boot-1b1ffda4207125c5bc618d4b0ca718b52cf7a4c0.zip | |
boot: android: Fix ramdisk loading for v2 header
Before
commit da3447d09fa0 ("android: Fix ramdisk loading for bootimage v3+"),
the ramdisk was loaded from img_data.ramdisk_ptr, ignoring offset
provided via mkbootimg.
commit da3447d09fa0 ("android: Fix ramdisk loading for bootimage v3+")
rightfully fixes this by switching to use img_data.ramdisk_addr instead.
However, it does not copy the ramdisk content to img_data.ramdisk_addr
in case we use boot image v2.
Because of this, we can no longer boot Android on Khadas vim3 board:
[ 3.940361] RAMDISK: Couldn't find valid RAM disk image starting at 0.
Add the missing memcpy() to fix the issue.
Fixes: da3447d09fa0 ("android: Fix ramdisk loading for bootimage v3+")
Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
Diffstat (limited to 'board')
0 files changed, 0 insertions, 0 deletions