All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Alrae <leon.alrae@imgtec.com>
To: Daniel Sanders <Daniel.Sanders@imgtec.com>,
	Vasileios Kalintiris <Vasileios.Kalintiris@imgtec.com>,
	Petar Jovanovic <petar.jovanovic@rt-rk.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] target-mips: add CPU definition for MIPS-II
Date: Tue, 16 Dec 2014 11:59:01 +0000	[thread overview]
Message-ID: <54901E85.8000100@imgtec.com> (raw)
In-Reply-To: <E484D272A3A61B4880CDF2E712E9279F4588121D@hhmail02.hh.imgtec.org>

Hi Daniel,

On 15/12/2014 14:03, Daniel Sanders wrote:
> Hi,
> 
>  
> 
> FWIW, the R6000 was a MIPS-II processor but I understand there was never
> a proper manual for it. http://www.linux-mips.org/wiki/R6000 has a small
> amount of information but not enough to accurately fill in qemu's structure.
> 
>  
> 
>> If this is really problematic for qemu, why don't we add an
>> --enable-experimental-targets, --enable-generic-targets or something
>> similar for generic/old CPU definitions?
> 
>  
> 
> One other possibility is to use a real CPU name such as R6000 but use
> reasonable guesses where information is unavailable. Is that a good
> compromise?

Adding R6000 sounds like the right way to go. Probably it won't be
accurately defined in QEMU until we can use the real hardware as a
reference, but this is still better than "MIPS-II generic CPU".

Thanks,
Leon

  parent reply	other threads:[~2014-12-16 11:59 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 ` [Qemu-devel] [PATCH] target-mips: add CPU definition for MIPS-II Petar Jovanovic
2014-12-15 10:08   ` 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 [this message]
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=54901E85.8000100@imgtec.com \
    --to=leon.alrae@imgtec.com \
    --cc=Daniel.Sanders@imgtec.com \
    --cc=Vasileios.Kalintiris@imgtec.com \
    --cc=petar.jovanovic@rt-rk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.