From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] Implement basic part of SA-1110/SA-1100
Date: Tue, 22 Mar 2011 19:08:03 +0300 [thread overview]
Message-ID: <AANLkTinOqOMcC9q0MeQ86HONr749Xf6TVBROdFp0c_AB@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikfkRtF5rOo_+d_AsKt=JGhb2ZYOadbW5asWKV1@mail.gmail.com>
Hello,
On 3/22/11, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 22 March 2011 14:53, Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
> wrote:
>
>> static inline int arm_feature(CPUARMState *env, int feature)
>> @@ -391,6 +392,19 @@ void cpu_arm_set_cp_io(CPUARMState *env, int cpnum,
>> #define ARM_CPUID_ARM946 0x41059461
>> #define ARM_CPUID_TI915T 0x54029152
>> #define ARM_CPUID_TI925T 0x54029252
>> +#define ARM_CPUID_SA1100 0x4401A11B
>> +#define ARM_CPUID_SA1100_B 0x4401A111
>> +#define ARM_CPUID_SA1100_C 0x4401A112
>> +#define ARM_CPUID_SA1100_D 0x4401A118
>> +#define ARM_CPUID_SA1100_E 0x4401A119
>> +#define ARM_CPUID_SA1100_G 0x4401A11B
>> +#define ARM_CPUID_SA1110 0x6901B119
>> +#define ARM_CPUID_SA1110_A0 0x6901B110
>> +#define ARM_CPUID_SA1110_B0 0x6901B114
>> +#define ARM_CPUID_SA1110_B1 0x6901B115
>> +#define ARM_CPUID_SA1110_B2 0x6901B116
>> +#define ARM_CPUID_SA1110_B4 0x6901B118
>> +#define ARM_CPUID_SA1110_B5 0x6901B119
>> #define ARM_CPUID_PXA250 0x69052100
>> #define ARM_CPUID_PXA255 0x69052d00
>> #define ARM_CPUID_PXA260 0x69052903
>
> Yikes. Do we really need 13 new strongarm CPU types?
> That's half again as many as we currently have defined
> for ARM CPUs of all flavours.
Just followed (more or less) PXA model. What do you suggest? Leave only the
latest ones?
>
>> @@ -1522,6 +1549,8 @@ void HELPER(set_cp15)(CPUState *env, uint32_t insn,
>> uint32_t val)
>> case 9:
>> if (arm_feature(env, ARM_FEATURE_OMAPCP))
>> break;
>> + if (arm_feature(env, ARM_FEATURE_STRONGARM))
>> + break; /* Ignore ReadBuffer access */
>> switch (crm) {
>> case 0: /* Cache lockdown. */
>> switch (op1) {
>
> I know we don't really have very good infrastructure for handling
> device-specific cp15 registers, but I'm not sure defining a new
> FEATURE_STRONGARM is the right approach here. (Yeah, it's just
> following ARM_FEATURE_OMAPCP but I don't like that either :-))
> I'll have a think about whether we can do something cleaner in
> this area (and indeed with the translate-time access checks).
Yeah, OMAPCP, XSCALE and IWMMX. Basically I'd need to plug
into cp15 regs: c9 (this one), c15 (later, idle/wait for interrupt) and
maybe c14 (debug: hwbp, data watch).
> PS: CODING_STYLE mandates braces on all if statements...
Looking around the code it doesn't seem so mandatory... I'll try
fixing my patches though.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2011-03-22 16:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 14:53 [Qemu-devel] [PATCH 1/2] Implement basic part of SA-1110/SA-1100 Dmitry Eremin-Solenikov
2011-03-22 14:53 ` [Qemu-devel] [PATCH 2/2] Basic implementation of Sharp Zaurus SL-5500 collie PDA Dmitry Eremin-Solenikov
2011-03-22 15:34 ` [Qemu-devel] [PATCH 1/2] Implement basic part of SA-1110/SA-1100 Peter Maydell
2011-03-22 16:08 ` Dmitry Eremin-Solenikov [this message]
2011-03-22 17:09 ` Peter Maydell
2011-03-22 18:46 ` [Qemu-devel] " Juan Quintela
-- strict thread matches above, loose matches on Subject: below --
2011-04-12 13:09 [Qemu-devel] [PATCH 0/2] StrongARM/Sharp Zaurus SL-5500 support Dmitry Eremin-Solenikov
2011-04-12 13:09 ` [Qemu-devel] [PATCH 1/2] Implement basic part of SA-1110/SA-1100 Dmitry Eremin-Solenikov
2011-04-12 21:32 ` Aurelien Jarno
2011-04-14 6:18 Dmitry Eremin-Solenikov
2011-04-16 9:25 ` Dmitry Eremin-Solenikov
2011-04-18 18:02 ` Aurelien Jarno
2011-04-19 14:53 ` Dmitry Eremin-Solenikov
2011-04-19 14:56 Dmitry Eremin-Solenikov
2011-04-20 11:00 ` Aurelien Jarno
2011-04-21 11:55 ` Dmitry Eremin-Solenikov
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=AANLkTinOqOMcC9q0MeQ86HONr749Xf6TVBROdFp0c_AB@mail.gmail.com \
--to=dbaryshkov@gmail.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).