From: linus.ml.walleij@gmail.com (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: make TCM allocation static and common for all archs
Date: Fri, 10 Sep 2010 20:45:09 +0200 [thread overview]
Message-ID: <AANLkTimn4mm+qJ8003v=no5uZj-_exiD3x9FK4c2fVt+@mail.gmail.com> (raw)
In-Reply-To: <20100910161621.GF21361@game.jcrosoft.org>
2010/9/10 Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>:
> Any feed back about the tcm?
None other than it works for me on U300 and RealView PB1176.
Some two people have mailed me in private and told me they're using
it for out-of-tree stuff (ARM 926 based I think.)
Alessandro Rubin tried to use it on the Nomadik NHK8815 but it
turns out that the "TCM" in that machine is actually a ROM and
a locked-down RAM that is used for some security stuff (not
TrustZone!).
Yours,
Linus Walleij
prev parent reply other threads:[~2010-09-10 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 23:16 [PATCH] ARM: make TCM allocation static and common for all archs Linus Walleij
2010-09-10 16:16 ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-10 18:45 ` Linus Walleij [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='AANLkTimn4mm+qJ8003v=no5uZj-_exiD3x9FK4c2fVt+@mail.gmail.com' \
--to=linus.ml.walleij@gmail.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 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).