From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <sha@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH master 3/7] ARM: configs: temporarily revive vexpress_defconfig
Date: Mon, 22 May 2023 10:36:32 +0200 [thread overview]
Message-ID: <650fe72b-6e37-a97a-2665-85980c1912ed@pengutronix.de> (raw)
In-Reply-To: <20230522082330.GK29365@pengutronix.de>
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@pengutronix.de>
>> ---
>> 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 |
next prev parent reply other threads:[~2023-05-22 8:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 5:22 [PATCH master 1/7] test: self: ramfs: fix unintended macro identifier confusion Ahmad Fatoum
2023-05-22 5:22 ` [PATCH master 2/7] include: zero_page: hide possibly NULL pointer variable from optimizer Ahmad Fatoum
2023-05-23 6:46 ` Ahmad Fatoum
2023-05-22 5:22 ` [PATCH master 3/7] ARM: configs: temporarily revive vexpress_defconfig Ahmad Fatoum
2023-05-22 8:23 ` Sascha Hauer
2023-05-22 8:36 ` Ahmad Fatoum [this message]
2023-05-22 5:22 ` [PATCH master 4/7] ARM64: configs: temporarily revive qemu_virt64_defconfig Ahmad Fatoum
2023-05-22 5:22 ` [PATCH master 5/7] pbl: have DEBUG_PBL depend only on PBL_CONSOLE Ahmad Fatoum
2023-05-22 5:22 ` [PATCH master 6/7] meminfo: avoid out-of-bounds compiler warning Ahmad Fatoum
2023-05-22 5:22 ` [PATCH master 7/7] console: don't fixup baud rate into earlycon string Ahmad Fatoum
2023-05-23 7:23 ` [PATCH master 1/7] test: self: ramfs: fix unintended macro identifier confusion Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=650fe72b-6e37-a97a-2665-85980c1912ed@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox