From: Antony Pavlov <antonynpavlov@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Paul Brook <paul@codesourcery.com>,
Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
Peter Maydell <peter.maydell@linaro.org>,
Alex Dumitrache <broscutamaker@gmail.com>,
g3gg0 <georg.hofstetter@lx-networking.de>,
Giovanni Condello <condellog@gmail.com>
Cc: qemu-devel@nongnu.org, Antony Pavlov <antonynpavlov@gmail.com>
Subject: [Qemu-devel] [RFC 1/5] target-arm: add ARM946E-S CPU
Date: Thu, 29 Aug 2013 13:33:49 +0400 [thread overview]
Message-ID: <1377768833-11400-2-git-send-email-antonynpavlov@gmail.com> (raw)
In-Reply-To: <1377768833-11400-1-git-send-email-antonynpavlov@gmail.com>
This is slightly altered version of ARM946E-S CPU code
from EOS QEMU (Magic Lantern project) so nearly all
credits go to @a1ex.
ARM946E-S Technical Reference Manual can be found here:
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0201d/index.html
Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
---
target-arm/cpu.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/target-arm/cpu.c b/target-arm/cpu.c
index b2556c6..409a311 100644
--- a/target-arm/cpu.c
+++ b/target-arm/cpu.c
@@ -322,6 +322,18 @@ static void arm926_initfn(Object *obj)
cpu->reset_sctlr = 0x00090078;
}
+static void arm946es_initfn(Object *obj)
+{
+ ARMCPU *cpu = ARM_CPU(obj);
+ set_feature(&cpu->env, ARM_FEATURE_V5);
+ set_feature(&cpu->env, ARM_FEATURE_MPU);
+ set_feature(&cpu->env, ARM_FEATURE_DUMMY_C15_REGS);
+ cpu->midr = 0x41059461;
+ cpu->ctr = (7 << 25) | (1 << 24) | (4 << 18) | (4 << 15) \
+ | (2 << 12) | (4 << 6) | (4 << 3) | (2 << 0);
+ cpu->reset_sctlr = 0x00000078;
+}
+
static void arm946_initfn(Object *obj)
{
ARMCPU *cpu = ARM_CPU(obj);
@@ -843,6 +855,7 @@ typedef struct ARMCPUInfo {
static const ARMCPUInfo arm_cpus[] = {
{ .name = "arm926", .initfn = arm926_initfn },
+ { .name = "arm946e-s", .initfn = arm946es_initfn },
{ .name = "arm946", .initfn = arm946_initfn },
{ .name = "arm1026", .initfn = arm1026_initfn },
/* What QEMU calls "arm1136-r2" is actually the 1136 r0p2, i.e. an
--
1.8.4.rc3
next prev parent reply other threads:[~2013-08-29 9:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 9:33 [Qemu-devel] [RFC 0/5] add initial support for Canon DIGIC SoC Antony Pavlov
2013-08-29 9:33 ` Antony Pavlov [this message]
2013-08-29 10:44 ` [Qemu-devel] [RFC 1/5] target-arm: add ARM946E-S CPU Peter Maydell
2013-08-29 10:52 ` Antony Pavlov
2013-08-29 18:17 ` Antony Pavlov
2013-08-30 5:09 ` Peter Crosthwaite
2013-08-30 7:29 ` Peter Maydell
2013-08-30 8:06 ` Antony Pavlov
2013-08-29 9:33 ` [Qemu-devel] [RFC 2/5] hw/arm: add very initial support for Canon DIGIC SoC Antony Pavlov
2013-08-29 12:15 ` Andreas Färber
2013-08-29 19:36 ` Antony Pavlov
2013-08-29 20:16 ` Peter Maydell
2013-08-30 5:07 ` Peter Crosthwaite
2013-08-30 8:10 ` Antony Pavlov
2013-08-30 17:53 ` Andreas Färber
2013-08-30 16:27 ` Andreas Färber
2013-08-29 14:29 ` Condello
2013-08-29 16:22 ` Antony Pavlov
2013-08-29 9:33 ` [Qemu-devel] [RFC 3/5] hw/arm/digic: add timer support Antony Pavlov
2013-08-29 9:33 ` [Qemu-devel] [RFC 4/5] hw/arm/digic: add UART support Antony Pavlov
2013-08-30 5:16 ` Peter Crosthwaite
2013-08-30 8:31 ` Antony Pavlov
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=1377768833-11400-2-git-send-email-antonynpavlov@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=broscutamaker@gmail.com \
--cc=condellog@gmail.com \
--cc=georg.hofstetter@lx-networking.de \
--cc=paul@codesourcery.com \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).