qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Petar Jovanovic" <petar.jovanovic@rt-rk.com>
To: 'Vasileios Kalintiris' <Vasileios.Kalintiris@imgtec.com>
Cc: 'Leon Alrae' <Leon.Alrae@imgtec.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-mips: add CPU definition for MIPS-II
Date: Tue, 2 Dec 2014 00:45:52 +0100	[thread overview]
Message-ID: <001501d00dc0$f1e038f0$d5a0aad0$@rt-rk.com> (raw)
In-Reply-To: <000e01d00dbf$36b8f4f0$a42aded0$@rt-rk.com>

[-- Attachment #1: Type: text/plain, Size: 1997 bytes --]

Adding (another) generic model for an old ISA revision is rather

discouraged in QEMU trunk. Can you add a particular real CPU model?

 

Regards,

Petar

________________________________________

From: Vasileios Kalintiris

Sent: 25 November 2014 11:04

To: address@hidden

Cc: Leon Alrae; address@hidden

Subject: [PATCH] target-mips: add CPU definition for MIPS-II

 

Add mips2-generic among CPU definitions for MIPS.

 

Signed-off-by: Vasileios Kalintiris <address@hidden>

---

target-mips/translate_init.c | 23 +++++++++++++++++++++++

1 file changed, 23 insertions(+)

 

diff --git a/target-mips/translate_init.c b/target-mips/translate_init.c

index 148b394..d4b1cd8 100644

--- a/target-mips/translate_init.c

+++ b/target-mips/translate_init.c

@@ -108,6 +108,29 @@ struct mips_def_t {

static const mips_def_t mips_defs[] =

{

     {

+        /* A generic CPU providing MIPS-II features.

+           FIXME: Eventually this should be replaced by a real CPU model.
*/

+        .name = "mips2-generic",

+        .CP0_PRid = 0x00018000,

+        .CP0_Config0 = MIPS_CONFIG0 | (MMU_TYPE_R4000 << CP0C0_MT),

+        .CP0_Config1 = MIPS_CONFIG1 | (1 << CP0C1_FP) | (15 << CP0C1_MMU) |

+                      (0 << CP0C1_IS) | (3 << CP0C1_IL) | (1 << CP0C1_IA) |

+                      (0 << CP0C1_DS) | (3 << CP0C1_DL) | (1 << CP0C1_DA) |

+                      (0 << CP0C1_CA),

+        .CP0_Config2 = MIPS_CONFIG2,

+        .CP0_Config3 = MIPS_CONFIG3,

+        .CP0_LLAddr_rw_bitmask = 0,

+        .CP0_LLAddr_shift = 4,

+        .SYNCI_Step = 32,

+        .CCRes = 2,

+        .CP0_Status_rw_bitmask = 0x30000011,

+        .CP1_fcr0 = (1 << FCR0_W) | (1 << FCR0_D) | (1 << FCR0_S),

+        .SEGBITS = 32,

+        .PABITS = 32,

+        .insn_flags = CPU_MIPS2,

+        .mmu_type = MMU_TYPE_R4000,

+    },

+    {

         .name = "4Kc",

         .CP0_PRid = 0x00018000,

         .CP0_Config0 = MIPS_CONFIG0 | (MMU_TYPE_R4000 << CP0C0_MT),

--

 

ping

 


[-- Attachment #2: Type: text/html, Size: 11259 bytes --]

       reply	other threads:[~2014-12-01 23:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000e01d00dbf$36b8f4f0$a42aded0$@rt-rk.com>
2014-12-01 23:45 ` Petar Jovanovic [this message]
2014-12-15 10:08   ` [Qemu-devel] [PATCH] target-mips: add CPU definition for MIPS-II Vasileios Kalintiris
2014-12-15 14:03     ` Daniel Sanders
2014-12-15 14:59       ` Petar Jovanovic
2014-12-16 10:16         ` Daniel Sanders
2014-12-16 11:59       ` Leon Alrae
2014-11-25 11:04 Vasileios Kalintiris
2014-12-01  9:51 ` Vasileios Kalintiris
2015-01-11  4:39 ` Maciej W. Rozycki

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='001501d00dc0$f1e038f0$d5a0aad0$@rt-rk.com' \
    --to=petar.jovanovic@rt-rk.com \
    --cc=Leon.Alrae@imgtec.com \
    --cc=Vasileios.Kalintiris@imgtec.com \
    --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).