On 22.05.23 10:23, Sascha Hauer wrote: > On Mon, May 22, 2023 at 07:22:18AM +0200, Ahmad Fatoum wrote: >> Vexpress and the Qemu ARM Virt platform have a memory-mapped flash >> starting at physical address 0. This clashes with the zero page used to >> trap NULL pointer accesses when MMU is enabled. For this reason, >> vexpress_defconfig disabled the MMU. vexpress_defconfig was removed in >> favor of multi_v7_defconfig, but the latter enables the MMU, breaking >> the ability to test barebox environment and state out of the box. >> >> Patches to resolve that are being upstreamed, so until they are, let's >> reinstate vexpress_defconfig. >> >> Signed-off-by: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx> >> --- >> Documentation/user/virtio.rst | 2 +- >> arch/arm/configs/vexpress_defconfig | 76 +++++++++++++++++++++++++++++ >> 2 files changed, 77 insertions(+), 1 deletion(-) >> create mode 100644 arch/arm/configs/vexpress_defconfig >> >> diff --git a/Documentation/user/virtio.rst b/Documentation/user/virtio.rst >> index a8624649f473..d944fa4821b1 100644 >> --- a/Documentation/user/virtio.rst >> +++ b/Documentation/user/virtio.rst >> @@ -44,7 +44,7 @@ Building barebox for QEMU targets is no different from others. >> For example, we can do the following with the CROSS_COMPILE environment >> variable being properly set to a working toolchain for ARM:: >> >> - $ make multi_v7_defconfig >> + $ make vexpress_defconfig >> $ make >> >> Testing >> diff --git a/arch/arm/configs/vexpress_defconfig b/arch/arm/configs/vexpress_defconfig > > vexpress_defconfig is not removed in master. The patch is still in > -next. I am fine with either taking this to next or dropping the original commit. > > Sascha > > -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
