All of lore.kernel.org
 help / color / mirror / Atom feed
From: tim.bird@am.sony.com (Tim Bird)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] arm: drop Execute-In-Place
Date: Thu, 5 May 2011 11:19:45 -0700	[thread overview]
Message-ID: <4DC2EA41.7030809@am.sony.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1105051413080.24613@xanadu.home>

On 05/05/2011 11:17 AM, Nicolas Pitre wrote:
> On Thu, 5 May 2011, Tim Bird wrote:
> 
>> On 05/05/2011 07:52 AM, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>> nearly no-one use it, only amop1, pxa and sa1100 implement it
>>
>> Sony uses this - a lot.  Principally we're using this on a NEC
>> naviengine part, which is ARM11MPCore based, support for which
>> is (sadly) out of tree.
>>
>> I'd like to see MORE support for XIP in the kernel, not less.
> 
> OK.  If done properly, there shouldn't be any need to drop XIP support.  
> However, given that XIP is already a specialized configuration that is 
> handled by hardware experts, in the future you might have to provide at 
> kernel configuration time the actual physical address of your RAM as it 
> is currently done for the ROM address where the kernel image is located.

That wouldn't be a problem.
The tools to set this up (make images) already have to hardcode
the physical addresses at build time, so adding it to the kernel
config is no big deal.
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Workgroup of the Linux Foundation
Senior Staff Engineer, Sony Network Entertainment
=============================

  reply	other threads:[~2011-05-05 18:19 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 14:52 [RFC PATCH] arm: drop Execute-In-Place Jean-Christophe PLAGNIOL-VILLARD
2011-05-05 15:17 ` Vitaly Wool
2011-05-05 15:38   ` Jean-Christophe PLAGNIOL-VILLARD
2011-05-05 18:00 ` Tim Bird
2011-05-05 18:03   ` Tim Bird
2011-05-05 18:03     ` Tim Bird
2011-05-05 18:32     ` David Woodhouse
2011-05-05 18:32       ` David Woodhouse
2011-05-05 18:40       ` Tim Bird
2011-05-05 18:40         ` Tim Bird
2011-05-05 18:54         ` Nicolas Pitre
2011-05-05 18:54           ` Nicolas Pitre
2011-05-05 19:04           ` Mike Frysinger
2011-05-05 19:04             ` Mike Frysinger
2011-05-05 19:12             ` Tim Bird
2011-05-05 19:12               ` Tim Bird
2011-05-05 19:27               ` Nicolas Pitre
2011-05-05 19:27                 ` Nicolas Pitre
2011-05-05 20:05                 ` Vitaly Wool
2011-05-05 20:05                   ` Vitaly Wool
2011-05-06  6:07                 ` Tony Lindgren
2011-05-06  6:07                   ` Tony Lindgren
2011-05-05 19:27               ` Mike Frysinger
2011-05-05 19:27                 ` Mike Frysinger
2011-05-05 20:25                 ` Tim Bird
2011-05-05 20:25                   ` Tim Bird
2011-05-05 20:31                   ` Mike Frysinger
2011-05-05 20:31                     ` Mike Frysinger
2011-05-06  5:17                     ` Jean-Christophe PLAGNIOL-VILLARD
2011-05-06  5:17                       ` Jean-Christophe PLAGNIOL-VILLARD
2011-05-05 18:17   ` Nicolas Pitre
2011-05-05 18:19     ` Tim Bird [this message]
2011-05-08 22:56   ` Linus Walleij

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=4DC2EA41.7030809@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.