From: Vitaly Wool <vitalywool@gmail.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Tim Bird <tim.bird@am.sony.com>,
Russell King <linux@arm.linux.org.uk>,
linux-embedded <linux-embedded@vger.kernel.org>,
Mike Frysinger <vapier.adi@gmail.com>,
Tony Lindgren <tony@atomide.com>,
David Woodhouse <dwmw2@infradead.org>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Eric Miao <eric.miao@canonical.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH] arm: drop Execute-In-Place
Date: Thu, 5 May 2011 22:05:12 +0200 [thread overview]
Message-ID: <BANLkTik7z+rJDCAaVo5uGgMhbtpWps453g@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1105051518580.24613@xanadu.home>
On Thu, May 5, 2011 at 9:27 PM, Nicolas Pitre <nicolas.pitre@linaro.org> wrote:
> Just to be clear... We have XIP in the tree already. If it is useful
> to someone, in-tree or out-of-tree, then it is worth keeping around.
> Even if the only user was out-of-tree which certainly wasn't the case
> when I added XIP support to the kernel, then ripping it out and adding
> it back later would be more trouble than preserving it.
>
> What I was asking recently is whether or not XIP is still useful to
> someone today. Apparently it is, which is the answer I was looking for.
Surely it is. The last thing I tried was the i.mx deviation which is
very much based on what's in the tree. It didn't work out without some
bits of hackery and I never got it straight enough to try upstreaming.
But nevertheless, IMO XIP is not dead and is not going to be in the
closest future.
~Vitaly
next prev parent reply other threads:[~2011-05-05 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1304607121-13612-1-git-send-email-plagnioj@jcrosoft.com>
[not found] ` <4DC2E5AA.5010604@am.sony.com>
2011-05-05 18:03 ` [RFC PATCH] arm: drop Execute-In-Place Tim Bird
2011-05-05 18:32 ` David Woodhouse
2011-05-05 18:40 ` Tim Bird
2011-05-05 18:54 ` Nicolas Pitre
2011-05-05 19:04 ` Mike Frysinger
2011-05-05 19:12 ` Tim Bird
2011-05-05 19:27 ` Nicolas Pitre
2011-05-05 20:05 ` Vitaly Wool [this message]
2011-05-06 6:07 ` Tony Lindgren
2011-05-05 19:27 ` Mike Frysinger
2011-05-05 20:25 ` Tim Bird
2011-05-05 20:31 ` Mike Frysinger
2011-05-06 5:17 ` Jean-Christophe PLAGNIOL-VILLARD
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=BANLkTik7z+rJDCAaVo5uGgMhbtpWps453g@mail.gmail.com \
--to=vitalywool@gmail.com \
--cc=dwmw2@infradead.org \
--cc=eric.miao@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.ferre@atmel.com \
--cc=nicolas.pitre@linaro.org \
--cc=plagnioj@jcrosoft.com \
--cc=tim.bird@am.sony.com \
--cc=tony@atomide.com \
--cc=vapier.adi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).