From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] AArch64: TCR_TG1_64K incorrectly sets TCR_EL1 bits [31:30]
Date: Wed, 02 Apr 2014 15:16:07 -0700 [thread overview]
Message-ID: <1396476967.32040.13.camel@joe-AO722> (raw)
In-Reply-To: <CAHWCVWKng7rwewi6f0Tf1=uZRGERe56W6vRUuyCVtLz-gSz-9Q@mail.gmail.com>
On Wed, 2014-04-02 at 17:10 -0500, Joe Sylve wrote:
> Should it? The reference manual refers to the architecture as AArch64.
>
> On Wed, Apr 2, 2014 at 4:44 PM, Joe Perches <joe@perches.com> wrote:
> > On Wed, 2014-04-02 at 18:07 +0100, Catalin Marinas wrote:
> >> On Wed, Apr 02, 2014 at 01:38:44PM +0100, Catalin Marinas wrote:
> >> > On Wed, Apr 02, 2014 at 05:00:38AM +0100, Joe Sylve wrote:
> >> > > Section D7.2.83 TCR_EL1, Translation Control Register (EL1) of the
> >> > > latest ARM Architecture Reference Manual, ARMv8, for ARMv8-A states
> >> > > that TCR_EL1 TG1 (bits [31:30]) should be set to 11 for a 64KB
> >> > > TTBR1_EL1 granule size. The mainline 3.14 kernel incorrectly sets
> >> > > those bits to 01 (which is a 16KB granule size).
> >
> > trivia:
> >
> > I think the subject title should be arm64
There was a fair amount of blowback about naming
the arch aarch64 in linux.
So for linux, the directory and arch name is arm64.
from: https://lkml.org/lkml/2012/7/15/133
From Linus Torvalds <>
Date Sun, 15 Jul 2012 16:53:21 -0700
- aarch64 is just another druggie name that the ARM people came up
with after drinking too much of the spiked water in cambridge.
next prev parent reply other threads:[~2014-04-02 22:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 4:00 [PATCH 1/1] AArch64: TCR_TG1_64K incorrectly sets TCR_EL1 bits [31:30] Joe Sylve
2014-04-02 12:38 ` Catalin Marinas
2014-04-02 17:07 ` Catalin Marinas
2014-04-02 17:21 ` Joe Sylve
2014-04-03 8:58 ` Catalin Marinas
2014-04-02 21:44 ` Joe Perches
2014-04-02 22:10 ` Joe Sylve
2014-04-02 22:16 ` Joe Perches [this message]
2014-04-02 23:01 ` Joe Sylve
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=1396476967.32040.13.camel@joe-AO722 \
--to=joe@perches.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).