qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Patch] target-ppc mtcrf instruction not recognized
Date: Sun, 15 May 2005 14:00:29 +0200	[thread overview]
Message-ID: <1116158429.12010.80.camel@rapid> (raw)
In-Reply-To: <4920FD1A-05D0-4A7C-BCE6-58036B198978@free.fr>

On Sat, 2005-05-14 at 21:03 +0200, Pierre d'Herbemont wrote:
> On 14 mai 05, at 20:15, J. Mayer wrote:
> 
> > Qemu assume all reserved fields are set to zero, not 1.
> 
> > PowerPC specifications says: (section 8.1 of PEM)
[...]
> > In the case of mtcrf, the PowerPC specification says the bits 11,  
> > 21 and
> > 31 (IBM notation) _must_ be zero.
> > This is what is described in 32 bits PEM as well as 64 bits PEM
> > (including the latest revision dated on 31/03/2005) and the 740/750
> > PowerPC user manual (which is the one currently emulated by Qemu).
> >
> > It would be acceptable to relax the check if it would make MacOS X  
> > 10.4 boot.
> > But in this case, only the bit 11 (which causes the problem here)  
> > should
> > be relaxed.
> > Then, the bit mask becomes 0x00000801 (not 0x00000000).
> 
[...]
> In fact I was referring to my old PowerPC Spec book in french from  
> IBM (titled Architecture PowerPC), this link was the first google  
> returned. After looking again in my book, I found what you said. I am  
> confused, I wrote this a bit quickly. But the fact remains, would you  
> send a correct patch for that? It'll definitely be compulsory in  
> order to boot Mac OS X 10.4, and for darwin-user.

OK, I did put this in my working repository and I'll submit this to
Fabrice.
Please try to do this change to check if other bits need to be relax or
not:

Index: target-ppc/translate.c
===================================================================
RCS file: /cvsroot/qemu/qemu/target-ppc/translate.c,v
retrieving revision 1.31
diff -u -r1.31 translate.c
--- target-ppc/translate.c      12 May 2005 18:46:11 -0000      1.31
+++ target-ppc/translate.c      14 May 2005 17:14:35 -0000
@@ -2123,7 +2123,7 @@
 }
 
 /* mtcrf */
-GEN_HANDLER(mtcrf, 0x1F, 0x10, 0x04, 0x00100801, PPC_MISC)
+GEN_HANDLER(mtcrf, 0x1F, 0x10, 0x04, 0x00000801, PPC_MISC)
 {
     gen_op_load_gpr_T0(rS(ctx->opcode));
     gen_op_store_cr(CRM(ctx->opcode));

And maybe someone should fill an Apple bug report to tell them their as
is buggy ;-)

-- 
J. Mayer <l_indien@magic.fr>
Never organized

  reply	other threads:[~2005-05-15 12:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-14 17:20 [Qemu-devel] [Patch] target-ppc mtcrf instruction not recognized Pierre d'Herbemont
2005-05-14 18:15 ` J. Mayer
2005-05-14 19:03   ` Pierre d'Herbemont
2005-05-15 12:00     ` J. Mayer [this message]
2005-05-16  7:54       ` Benjamin Herrenschmidt
2005-05-17 20:17         ` Pierre d'Herbemont
2005-05-17 21:10         ` J. Mayer
2005-05-18  9:06           ` Herbert Poetzl
2005-05-18 10:28             ` J. Mayer
     [not found]       ` <da63183705051610384e40c3de@mail.gmail.com>
     [not found]         ` <da631837050516110638c65163@mail.gmail.com>
2005-05-16 21:14           ` J. Mayer

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=1116158429.12010.80.camel@rapid \
    --to=l_indien@magic.fr \
    --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).