From: Thomas Huth <thuth@redhat.com>
To: Greg Kurz <groug@kaod.org>
Cc: "Murilo Opsfelder Araújo" <muriloo@linux.vnet.ibm.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 0/2] Clean up the ppc default configs
Date: Mon, 15 Jan 2018 15:26:21 +0100 [thread overview]
Message-ID: <d3eeebf8-c94c-09dc-3d3d-0933dcedb8af@redhat.com> (raw)
In-Reply-To: <20180115120543.1f825292@bahia.lan>
On 15.01.2018 12:05, Greg Kurz wrote:
> On Mon, 15 Jan 2018 10:30:53 +0100
> Thomas Huth <thuth@redhat.com> wrote:
>
>> ppc64-softmmu is a superset of ppc-softmmu which in turn is a superset
>
> Hi Thomas,
>
> Per curiosity. I understand that a 64-bit ppc CPU is expected to support
> 32-bit ppc code, but does QEMU really need to emulate setups that likely
> never existed in real life (like a PowerMac G5 or a pSeries with an
> internal floppy disk controller for example) ?
I think the CONFIG_FDC switch is there for the PReP machine, not for the
Macs.
Thomas
next prev parent reply other threads:[~2018-01-15 14:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 9:30 [Qemu-devel] [PATCH 0/2] Clean up the ppc default configs Thomas Huth
2018-01-15 9:30 ` [Qemu-devel] [PATCH 1/2] default-configs/ppc64-softmmu: Include 32-bit configs instead of copying them Thomas Huth
2018-01-15 9:30 ` [Qemu-devel] [PATCH 2/2] default-configs/ppc-softmmu: Restructure the switches according to the machines Thomas Huth
2018-01-15 11:05 ` [Qemu-devel] [Qemu-ppc] [PATCH 0/2] Clean up the ppc default configs Greg Kurz
2018-01-15 14:26 ` Thomas Huth [this message]
2018-01-15 12:00 ` BALATON Zoltan
2018-01-15 14:38 ` Thomas Huth
2018-01-16 10:41 ` Thomas Huth
2018-01-16 10:51 ` Peter Maydell
2018-01-16 11:10 ` Thomas Huth
2018-01-15 13:01 ` [Qemu-devel] " Peter Maydell
2018-01-15 14:42 ` [Qemu-devel] [Qemu-ppc] " Thomas Huth
2018-01-16 1:19 ` David Gibson
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=d3eeebf8-c94c-09dc-3d3d-0933dcedb8af@redhat.com \
--to=thuth@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=muriloo@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).