qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Magnus Damm" <magnus.damm@gmail.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] target-sh4: Support CPU versioning.
Date: Wed, 5 Dec 2007 23:32:12 +0900	[thread overview]
Message-ID: <aec7e5c30712050632l2648f26dk4d9e67f1af817ea1@mail.gmail.com> (raw)
In-Reply-To: <20071203084020.GA9284@linux-sh.org>

On Dec 3, 2007 5:40 PM, Paul Mundt <lethal@linux-sh.org> wrote:
> Trivial patch adding CPU listing and the ability to do per-subtype
> CVR/PVR/PRR values. The existing semantics aren't changed, as only
> the SH7751R values are stubbed in for the moment, but the kernel is at
> least able to get the cache probing correct.
>
> This also makes it trivial to abstract subtype specific registers like
> MMU_PTEA and to set up feature bits in line with the kernel probing for
> things like conditionalizing FPU/DSP context.
>
> Signed-off-by: Paul Mundt <lethal@linux-sh.org>

Thank you for implementing this. Good idea. There is however a small
glitch introduced with this patch - both the r2d and the shix board
can pass "any" as cpu string when calling cpu_init(). This results in
a "Unable to find CPU definition" error unless the cpu type is
specified on the command line using the -cpu option. Maybe a better
solution would be to pass "SH7751R" from r2d and "SH7750" from shix by
default?

/ magnus

      reply	other threads:[~2007-12-05 14:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03  8:40 [Qemu-devel] [PATCH] target-sh4: Support CPU versioning Paul Mundt
2007-12-05 14:32 ` Magnus Damm [this message]

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=aec7e5c30712050632l2648f26dk4d9e67f1af817ea1@mail.gmail.com \
    --to=magnus.damm@gmail.com \
    --cc=lethal@linux-sh.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).