From: Antony Pavlov <antonynpavlov@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Alex Dumitrache <broscutamaker@gmail.com>,
Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
Giovanni Condello <condellog@gmail.com>,
g3gg0 <georg.hofstetter@lx-networking.de>,
QEMU Developers <qemu-devel@nongnu.org>,
Paul Brook <paul@codesourcery.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC 1/5] target-arm: add ARM946E-S CPU
Date: Thu, 29 Aug 2013 22:17:40 +0400 [thread overview]
Message-ID: <20130829221740.a55c8613997966c2322a2a52@gmail.com> (raw)
In-Reply-To: <CAFEAcA89cieXvNbs1f822q9mw0oAP2jTNrzmk08dCV8YrkT=JA@mail.gmail.com>
On Thu, 29 Aug 2013 11:44:38 +0100
Peter Maydell <peter.maydell@linaro.org> wrote:
> On 29 August 2013 10:33, Antony Pavlov <antonynpavlov@gmail.com> wrote:
> > 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
>
> I think the CPU we label "arm946" *is* an ARM946E-S -- there's
> no other TRM or variant of the 946 listed on the ARM website.
> If we're inaccurate about something we should just fix it (and
> that should be safe since there's no existing board model which
> uses the 946).
I have just run barebox on conventional "arm946" qemu CPU. It works fine.
IMHO just now we can drop this patch.
If Magic Lantern or CHDK need some specific initial CPU CP15 register state
then we can fix it in the platform code without defining new CPU type.
Any comments?
--
Best regards,
Antony Pavlov
next prev parent reply other threads:[~2013-08-29 18:20 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 ` [Qemu-devel] [RFC 1/5] target-arm: add ARM946E-S CPU Antony Pavlov
2013-08-29 10:44 ` Peter Maydell
2013-08-29 10:52 ` Antony Pavlov
2013-08-29 18:17 ` Antony Pavlov [this message]
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=20130829221740.a55c8613997966c2322a2a52@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).