Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Guido Martínez" <guido@vanguardiasur.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/6] arm: update processor types
Date: Tue, 19 May 2015 12:53:42 -0300	[thread overview]
Message-ID: <20150519155342.GA23051@fox> (raw)
In-Reply-To: <20150518220512.556d53ae@free-electrons.com>

On Mon, May 18, 2015 at 10:05:12PM +0200, Thomas Petazzoni wrote:
> >  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
> 
> This breaks things, because now BR2_USE_MMU is empty on architectures
> others than arm, armeb, sh and xtensa.
Ugh, stupid me.

> What we probably need is something like this:
> 
> config BR2_ARCH_MMU_OPTIONAL
> 	bool
> 
> config BR2_ARCH_MMU_MANDATORY
> 	bool
> 
> and have all ARM cores select BR2_ARCH_MMU_OPTIONAL except Cortex M3,
> SuperH and Xtensa select BR2_ARCH_MMU_OPTIONAL, all other architectures
> except Blackfin selecting BR2_ARCH_MMU_MANDATORY.
> 
> And then:
> 
> 	bool "Enable MMU support" if BR2_ARCH_MMU_OPTIONAL
> 	default y if BR2_ARCH_MMU_MANDATORY || BR2_ARCH_MMU_OPTIONAL
> 
> or something like that.
Yes, I'll work on something like that.

Sorry for the noise :(

-- 
Guido Mart?nez, VanguardiaSur
www.vanguardiasur.com.ar

  reply	other threads:[~2015-05-19 15:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 14:24 [Buildroot] [PATCH v2 0/6] Add ARM Cortex-M3 support Guido Martínez
2015-05-18 14:24 ` [Buildroot] [PATCH v2 1/6] arm: update processor types Guido Martínez
2015-05-18 20:05   ` Thomas Petazzoni
2015-05-19 15:53     ` Guido Martínez [this message]
2015-05-21 16:51       ` Guido Martínez
2015-05-18 14:24 ` [Buildroot] [PATCH v2 2/6] pkg-utils: implement INFLATE for .deb files Guido Martínez
2015-05-18 19:55   ` Thomas Petazzoni
2015-05-19 16:00     ` Guido Martínez
2015-05-18 14:24 ` [Buildroot] [PATCH v2 3/6] toolchain: allow for stupid toolchains Guido Martínez
2015-05-18 14:24 ` [Buildroot] [PATCH v2 4/6] toolchain: introduce BR2_TOOLCHAIN_HAS_RESOLVER Guido Martínez
2015-05-18 14:24 ` [Buildroot] [PATCH v2 5/6] nommu/flat: don't add -elf2flt for some toolchains Guido Martínez
2015-05-18 19:58   ` Thomas Petazzoni
2015-05-19 19:00     ` Guido Martínez
2015-05-18 14:24 ` [Buildroot] [PATCH v2 6/6] toolchain-external: add OSELAS 2014.12.0 Cortex-M3 toolchain Guido Martínez

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=20150519155342.GA23051@fox \
    --to=guido@vanguardiasur.com.ar \
    --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