From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Dmitry Osipenko <digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Alexandre Courbot
<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ARM: trusted_foundations: Maintain CPU endianness
Date: Fri, 20 Mar 2015 10:07:07 -0600 [thread overview]
Message-ID: <550C45AB.3070703@wwwdotorg.org> (raw)
In-Reply-To: <1426865807-22981-1-git-send-email-digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 03/20/2015 09:36 AM, Dmitry Osipenko wrote:
> Convert CPU reset vector address to LE to support big-endian kernel.
Naively this sounds a little odd; the value here is in a CPU register
all the time, not in memory, so I'm not sure why endianness is relevant?
Presumably the CPU doesn't end up byte-swapping values in registers when
running in BE mode or it takes an SMC? If it does, why don't we need
cpu_to_le32(TF_SET_CPU_BOOT_ADDR_SMC) too?
Sorry if this is a silly question; I haven't followed any of the BE
kernel patches.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: trusted_foundations: Maintain CPU endianness
Date: Fri, 20 Mar 2015 10:07:07 -0600 [thread overview]
Message-ID: <550C45AB.3070703@wwwdotorg.org> (raw)
In-Reply-To: <1426865807-22981-1-git-send-email-digetx@gmail.com>
On 03/20/2015 09:36 AM, Dmitry Osipenko wrote:
> Convert CPU reset vector address to LE to support big-endian kernel.
Naively this sounds a little odd; the value here is in a CPU register
all the time, not in memory, so I'm not sure why endianness is relevant?
Presumably the CPU doesn't end up byte-swapping values in registers when
running in BE mode or it takes an SMC? If it does, why don't we need
cpu_to_le32(TF_SET_CPU_BOOT_ADDR_SMC) too?
Sorry if this is a silly question; I haven't followed any of the BE
kernel patches.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Alexandre Courbot <gnurou@gmail.com>,
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 10:07:07 -0600 [thread overview]
Message-ID: <550C45AB.3070703@wwwdotorg.org> (raw)
In-Reply-To: <1426865807-22981-1-git-send-email-digetx@gmail.com>
On 03/20/2015 09:36 AM, Dmitry Osipenko wrote:
> Convert CPU reset vector address to LE to support big-endian kernel.
Naively this sounds a little odd; the value here is in a CPU register
all the time, not in memory, so I'm not sure why endianness is relevant?
Presumably the CPU doesn't end up byte-swapping values in registers when
running in BE mode or it takes an SMC? If it does, why don't we need
cpu_to_le32(TF_SET_CPU_BOOT_ADDR_SMC) too?
Sorry if this is a silly question; I haven't followed any of the BE
kernel patches.
next prev parent reply other threads:[~2015-03-20 16:07 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
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 [this message]
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=550C45AB.3070703@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.