From: Dmitry Osipenko <digetx@gmail.com>
To: Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
Alexandre Courbot <gnurou@gmail.com>
Cc: linux-tegra@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: trusted_foundations: Maintain CPU endianness
Date: Fri, 20 Mar 2015 18:47:18 +0300 [thread overview]
Message-ID: <550C4106.4090801@gmail.com> (raw)
In-Reply-To: <1426865807-22981-1-git-send-email-digetx@gmail.com>
This patch not tested. I assume that firmware save/restore cp15 context, i.e. it
doesn't require switching to LE before smc call and restore endianness after.
--
Dmitry
WARNING: multiple messages have this Message-ID (diff)
From: digetx@gmail.com (Dmitry Osipenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: trusted_foundations: Maintain CPU endianness
Date: Fri, 20 Mar 2015 18:47:18 +0300 [thread overview]
Message-ID: <550C4106.4090801@gmail.com> (raw)
In-Reply-To: <1426865807-22981-1-git-send-email-digetx@gmail.com>
This patch not tested. I assume that firmware save/restore cp15 context, i.e. it
doesn't require switching to LE before smc call and restore endianness after.
--
Dmitry
next prev parent reply other threads:[~2015-03-20 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 15:36 [PATCH] ARM: trusted_foundations: Maintain CPU endianness Dmitry Osipenko
2015-03-20 15:36 ` Dmitry Osipenko
2015-03-20 15:36 ` Dmitry Osipenko
2015-03-20 15:47 ` Dmitry Osipenko [this message]
2015-03-20 15:47 ` Dmitry Osipenko
[not found] ` <550C4106.4090801-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-03-20 16:20 ` Dave Martin
2015-03-20 16:20 ` Dave Martin
2015-03-20 16:20 ` Dave Martin
[not found] ` <1426865807-22981-1-git-send-email-digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-03-20 16:07 ` Stephen Warren
2015-03-20 16:07 ` Stephen Warren
2015-03-20 16:07 ` Stephen Warren
[not found] ` <550C45AB.3070703-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2015-03-20 16:41 ` Dmitry Osipenko
2015-03-20 16:41 ` Dmitry Osipenko
2015-03-20 16:41 ` Dmitry Osipenko
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=550C4106.4090801@gmail.com \
--to=digetx@gmail.com \
--cc=gnurou@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@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 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.