From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH] arch/Config.in: armeb no-MMU is not supported
Date: Thu, 9 Jun 2022 22:31:46 +0200 [thread overview]
Message-ID: <20220609223146.6c6185e4@windsurf> (raw)
In-Reply-To: <20220608094803.3403930-1-thomas.petazzoni@bootlin.com>
On Wed, 8 Jun 2022 11:48:02 +0200
Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:
> elf2flt does not support ARM big-endian, so supporting Cortex M3/M4/M7
> with armeb is not possibly.
>
> Therefore this commit makes:
>
> - MMU mandatory on armeb
> - Prevents from seeing Cortex M3/M4/M7 on armeb
>
> Fixes:
>
> http://autobuild.buildroot.net/results/9bca0cbfb6a66c455e74ad194526bca942665978/
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> arch/Config.in | 2 +-
> arch/Config.in.arm | 3 +++
> 2 files changed, 4 insertions(+), 1 deletion(-)
I have mistakenly pushed my own patch, sorry about this. Hopefully
people are OK with this, if not I can revert. Let me know.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-06-09 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 9:48 [Buildroot] [PATCH] arch/Config.in: armeb no-MMU is not supported Thomas Petazzoni via buildroot
2022-06-09 20:31 ` Thomas Petazzoni via buildroot [this message]
2022-06-19 13:00 ` Peter Korsgaard
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=20220609223146.6c6185e4@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.