Skip to content

Allow booting a 32-bit system with a top memory address beyond 4 GiB

Bin Meng u-boot 3 versions – New

Get series with b4
b4 am CAEUhbmUE_iOwT++M1b7KONAiY7VzWWykPnamqGXV_WJfGKLgyQ@mail.gmail.com

Versions newest first · linked by author and title

  1. v2 Latest posting 2/20 of 10 patches 0 repliesNew
  2. v2 posting 1/210 patches 0 repliesSuperseded
  3. v17 patches 0 repliesSuperseded

Patches in v2 posting 2/2 No applies recorded yet

None of the 10 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [PATCH v2 00/10] Allow booting a 32-bit system with a top memory address beyond 4 GiB

Hi Simon,

Quoted 9 lines · Bin Meng

When testing QEMU RISC-V 'virt' machine with a 2 GiB memory configuration, it was discovered gd->ram_top is assigned to value zero in setup_dest_addr().

While 2 GiB QEMU RISC-V 'virt' happens to work with U-Boot today, increasing more memory doesn't make a bootable system. There are various places in U-Boot that prevents such from working.

Quoted 8 lines

While this is seen and tested on RISC-V, it's not RISC-V centric, but a generic issue that may affect all architectures.

Changes in v2:
- new patch: arm: rockchip: Explicitly cast gd->ram_top in dram_init_banksize()
- new patch: riscv: ax25-ae350: Cast addr with uintptr_t
- new patch: net: ftmac100: Cast priv->iobase with uintptr_t

GitLab pass:
https://gitlab.denx.de/u-boot/custodians/u-boot-x86/-/pipelines/6148

Azure pass with the patch [1]:
https://dev.azure.com/bmeng/GitHub/_build/results?buildId=312&view=results

[1] http://patchwork.ozlabs.org/project/uboot/patch/20210131083835.9916-1-bmeng.cn at gmail.com/

Regards,
Bin