Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] xtensa: add support for the Xtensa architecture
Date: Sat, 10 Nov 2012 01:33:33 +0100	[thread overview]
Message-ID: <509DA0DD.3040904@mind.be> (raw)
In-Reply-To: <509D9F95.1040806@zankel.net>

On 11/10/12 01:28, Chris Zankel wrote:
> On 11/08/2012 01:01 PM, Arnout Vandecappelle wrote:
>> >  On 11/08/12 04:38, Chris Zankel wrote:
>>> >>     config BR2_USE_MMU
>>> >>  -	bool "Enable MMU support" if BR2_arm || BR2_armeb || BR2_mips || BR2_mipsel || BR2_sh
>>> >>  +	bool "Enable MMU support" if BR2_arm || BR2_armeb || BR2_mips || BR2_mipsel || BR2_sh || BR2_xtensa
>>> >>     	default y if !BR2_bfin
>> >     So the Xtensa, a configurable processor, always has a MMU?
> Good point. Actually, you can configure Xtensa with and without an MMU,
> so I think the above logic is correct. It allows to configure MMU if the
> processor is Xtensa, am I wrong?

  Err, yes, I was misreading the patch... Sorry about that.

  Regards,
  Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2012-11-10  0:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08  3:38 [Buildroot] [PATCH 1/2] xtensa: add support for the Xtensa architecture Chris Zankel
2012-11-08 21:01 ` Arnout Vandecappelle
2012-11-10  0:28   ` Chris Zankel
2012-11-10  0:33     ` Arnout Vandecappelle [this message]

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=509DA0DD.3040904@mind.be \
    --to=arnout@mind.be \
    --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