From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] arm: update processor types
Date: Sat, 14 Feb 2015 14:51:58 +0100 [thread overview]
Message-ID: <54DF52FE.2070603@openwide.fr> (raw)
In-Reply-To: <54D653E2.2080305@vanguardiasur.com.ar>
Hi Ezequiel,
[snip]
>>> diff --git a/toolchain/toolchain-common.in b/toolchain/toolchain-common.in
>>> index 2ee2019..fd6ef53 100644
>>> --- a/toolchain/toolchain-common.in
>>> +++ b/toolchain/toolchain-common.in
>>> @@ -114,8 +114,10 @@ config BR2_NEEDS_GETTEXT_IF_LOCALE
>>> default y if (BR2_NEEDS_GETTEXT && BR2_ENABLE_LOCALE)
>>>
>>> config BR2_USE_MMU
>>> - bool "Enable MMU support" if BR2_arm || BR2_armeb || BR2_sh || BR2_xtensa
>>> - default y if !BR2_bfin
>>> + bool "Enable MMU support"
>>> + depends on BR2_arm || BR2_armeb || BR2_sh || BR2_xtensa
>>> + depends on !BR2_cortex_m3 && !BR2_bfin
>>> + default y
>>
>> And here with BR2_ARCH_HAS_MMU_SUPPORT ?
>>
Sorry for the delay...
>
> Hm.. shouldn't that be, BR2_ARCH_HAS_OPTIONAL_MMU or something ?
>
> At least that's what it seems: only some architectures expose the build
> time config to disable MMU.
>
I think we need BR2_ARCH_HAS_MMU_SUPPORT if there is an MMU in the CPU and
BR2_ARCH_HAS_OPTIONAL_MMU if the MMU can be disabled.
The BR2_ARCH_HAS_OPTIONAL_MMU should automatically select
BR2_ARCH_HAS_MMU_SUPPORT when set to y.
Then BR2_arm, BR2_armeb, BR2_sh and BR2_xtensa should select
BR2_ARCH_HAS_OPTIONAL_MMU.
And all other architecture should select BR2_ARCH_HAS_MMU_SUPPORT except
BR2_bfin and BR2_cortex_m3.
So BR2_USE_MMU look like this:
config BR2_USE_MMU
boot "Enable MMU support" if BR2_ARCH_HAS_OPTIONAL_MMU
default y if BR2_ARCH_HAS_MMU_SUPPORT
When looking again at your patch, there is an error when another architecture
like i386 is selected.
BR2_USE_MMU must be set to y in that case.
What do you think ?
Best regards,
Romain
next prev parent reply other threads:[~2015-02-14 13:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 18:33 [Buildroot] [PATCH 0/4] ARM Cortex-M3 support Ezequiel Garcia
2015-01-22 18:33 ` [Buildroot] [PATCH 1/4] arm: conditionally support regular ARM instructions Ezequiel Garcia
2015-02-02 16:17 ` Romain Naour
2015-02-02 20:18 ` Thomas Petazzoni
2015-01-22 18:33 ` [Buildroot] [PATCH 2/4] arm: update processor types Ezequiel Garcia
2015-02-02 16:18 ` Romain Naour
2015-02-07 18:05 ` Ezequiel Garcia
2015-02-14 13:51 ` Romain Naour [this message]
2015-02-07 19:47 ` Ezequiel Garcia
2015-02-14 14:43 ` Romain Naour
2015-01-22 18:33 ` [Buildroot] [PATCH 3/4] toolchain: allow for stupid toolchains Ezequiel Garcia
2015-01-25 19:32 ` Thomas Petazzoni
2015-02-02 16:18 ` Romain Naour
2015-02-02 17:32 ` Yann E. MORIN
2015-01-22 18:33 ` [Buildroot] [PATCH 4/4] toolchain-external: add OSELAS 2013.12.2 Cortex-M3 toolchain Ezequiel Garcia
2015-02-02 16:29 ` Romain Naour
2015-02-02 20:19 ` [Buildroot] [PATCH 0/4] ARM Cortex-M3 support Thomas Petazzoni
2015-02-03 1:05 ` Ezequiel Garcia
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=54DF52FE.2070603@openwide.fr \
--to=romain.naour@openwide.fr \
--cc=buildroot@busybox.net \
/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