From: "Hervé Poussineau" <hpoussin@reactos.org>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: Julio Guerra <guerr@julio.in>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 7/7] prep: QOM'ify System I/O
Date: Sat, 04 May 2013 11:38:03 +0200 [thread overview]
Message-ID: <5184D6FB.1090606@reactos.org> (raw)
In-Reply-To: <5183A13B.2030108@web.de>
Andreas Färber a écrit :
> Am 02.05.2013 22:09, schrieb Hervé Poussineau:
>> Most of the functionality is extracted from hw/ppc/prep.c.
>> Also add support for board identification/equipment registers.
>>
>> Document it for the IBM 43p emulation.
>>
>> Cc: Julio Guerra <guerr@julio.in>
>> Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
>> ---
>> docs/ibm_43p.cfg | 5 +
>> hw/ppc/Makefile.objs | 1 +
>> hw/ppc/prep_systemio.c | 298 ++++++++++++++++++++++++++++++++++++++++++++++++
>> trace-events | 4 +
>> 4 files changed, 308 insertions(+)
>> create mode 100644 hw/ppc/prep_systemio.c
>
> Haven't reviewed the full patch yet, but since this is not modifying
> hw/ppc/prep.c, it is duplicating code rather than QOM'ifying the
> existing code.
>
> Have you looked into Julio's patch whom you CC? I'm still not sure how
> to solve things for 1.5 (and this series a consider -next).
Yes, I've partly taken Julio's patch into account, ie port 0x92 is now
read/write. However, I didn't change the way the reset is done due to
missing agrement of how it should be done: "this is touching on the same
soft reset topic that I am awaiting the outcome for x86". [1]
Moreover, registers emulated are not exactly the same as in hw/ppc/prep.c:
Registers not present in hw/ppc/prep_systemio.c:
0x800: Motorola CPU configuration register
0x802: Motorola base module feature register
0x803: Motorola base module status register
0x823: Something related to no L2 cache?
Those seem specific to Motorola, so they probably belong to another device.
New registers added to hw/ppc/prep_systemio.c:
0x818: Key lock (Read Only)
0x852: System Board Identification (Read Only)
I'm not really sure of impacts of changing 'prep' machine to remove some
registers and adding new ones, so I prefered to keep it as is. However,
if you think that I should use the QOM'ified System I/O device in 'prep'
machine (and this will change emulated machine), I'll do it.
Hervé
[1] https://lists.gnu.org/archive/html/qemu-devel/2013-04/msg03359.html
prev parent reply other threads:[~2013-05-04 9:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 20:08 [Qemu-devel] [PATCH 0/7] ppc/prep: add IBM RS/6000 43p machine Hervé Poussineau
2013-05-02 20:08 ` [Qemu-devel] [PATCH 1/7] pci: add MPC105 PCI host bridge emulation Hervé Poussineau
2013-05-02 21:01 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2013-05-03 5:57 ` Hervé Poussineau
2013-05-06 15:01 ` Alexander Graf
2013-05-06 20:57 ` Hervé Poussineau
2013-05-06 22:16 ` Alexander Graf
2013-05-06 22:41 ` Andreas Färber
2013-05-07 5:48 ` Hervé Poussineau
2013-05-09 17:47 ` Blue Swirl
2013-05-02 20:08 ` [Qemu-devel] [PATCH 2/7] qom: handle registration of new types when initializing the first ones Hervé Poussineau
2013-05-03 11:46 ` Andreas Färber
2013-05-05 8:38 ` Hervé Poussineau
2013-05-02 20:09 ` [Qemu-devel] [PATCH 3/7] m48t59: move ISA ports/memory regions registration to QOM constructor Hervé Poussineau
2013-05-02 20:09 ` [Qemu-devel] [PATCH 4/7] m48t59: register a QOM type for each nvram type we support Hervé Poussineau
2013-05-02 21:29 ` Artyom Tarasenko
2013-05-03 5:50 ` Hervé Poussineau
2013-05-03 23:16 ` Artyom Tarasenko
2013-05-04 5:24 ` Hervé Poussineau
2013-05-02 20:09 ` [Qemu-devel] [PATCH 5/7] m48t59: add a Nvram interface Hervé Poussineau
2013-05-02 20:09 ` [Qemu-devel] [PATCH 6/7] prep: add IBM RS/6000 7248 (43p) machine emulation Hervé Poussineau
2013-05-02 20:09 ` [Qemu-devel] [PATCH 7/7] prep: QOM'ify System I/O Hervé Poussineau
2013-05-03 11:36 ` Andreas Färber
2013-05-04 9:38 ` Hervé Poussineau [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=5184D6FB.1090606@reactos.org \
--to=hpoussin@reactos.org \
--cc=andreas.faerber@web.de \
--cc=guerr@julio.in \
--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 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.