From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: "M. Warner Losh" <imp@bsdimp.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fix configure for mips o32
Date: Wed, 03 Jun 2009 17:17:12 +0200 [thread overview]
Message-ID: <871vq1uz2f.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <20090603.082920.514365571.imp@bsdimp.com> (M. Warner Losh's message of "Wed\, 03 Jun 2009 08\:29\:20 -0600 \(MDT\)")
"M. Warner Losh" <imp@bsdimp.com> writes:
> In message: <87prdlv6wf.fsf@lechat.rtp-net.org>
> Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org> writes:
> : The commit 1ad2134f914dfd4c8f92307c94c9a5a1e28f0059 is defining
> : target_phys_bits and set it to 64 for all mips machines including mipsel
> : machines which are 32 bit. This patch set it to 32.
>
> But R4000PC and R4400PC machines ran in Little Endian mode and had
> 64-bit registers.
>
> It is only the recent mips32 and mips32r2 machines that have 32-bit
> registers...
I'm sorry but I don't get your point. Qemu should work on all cpu. 4Kc &
friends are currently supports (according to the -M switch) and iirc
theses beasts have 32bit address path not 64. I really fear that setting
64 will break them. That's why I've sent this patch. If keeping 64bit
breaks 4Kc and if switching to 32 break r4k, an other solution will have
to be found imho
Arnaud
next prev parent reply other threads:[~2009-06-03 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 12:28 [Qemu-devel] [PATCH] fix configure for mips o32 Arnaud Patard
2009-06-03 14:29 ` M. Warner Losh
2009-06-03 15:17 ` Arnaud Patard [this message]
2009-06-03 14:46 ` Paul Brook
2009-06-03 15:20 ` Arnaud Patard
2009-06-03 15:22 ` Paul Brook
2009-06-04 9:18 ` Arnaud Patard
2009-06-05 7:29 ` M. Warner Losh
2009-06-03 15:34 ` M. Warner Losh
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=871vq1uz2f.fsf@lechat.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--cc=imp@bsdimp.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).