From: "Hervé Poussineau" <hpoussin@reactos.org>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org, agraf@suse.de,
afaerber@suse.de, atar4qemu@gmail.com
Subject: Re: [Qemu-devel] [PATCH 0/2] m48t59: add year offset and MMIO ISA mapping
Date: Mon, 19 Jan 2015 22:59:17 +0100 [thread overview]
Message-ID: <54BD7E35.40108@reactos.org> (raw)
In-Reply-To: <1421667328-11800-1-git-send-email-mark.cave-ayland@ilande.co.uk>
Le 19/01/2015 12:35, Mark Cave-Ayland a écrit :
> This patch lays the groundwork for switching sun4u over from ioport NVRAM
> access to MMIO NVRAM access.
>
> Patch 1 introduces a new year_offset property which is the offset between the
> year value stored in hardware and the actual year. In particular, Sun hardware
> has a 68 year offset used to extend the date range of the IC. While the
> kernel sources I have viewed contain this offset within a #ifdef CONFIG_SPARC
> block, I've updated all the callers so that no change in behaviour will be
> seen across all platforms. PPC users may wish to alter the callers to change
> this behaviour as required.
>
> Patch 2 mimics the mem_base parameter from m48t59_init() to m48t59_init_isa()
> so that MMIO can be used for sun4u where the NVRAM is attached to the ebus
> which is essentially the same as an ISA bus.
I've a patch which QOM'ifies m48t59, that I'll send to the list.
If you apply it, you'll be then able to create a sysbus-m48t02 device, and then to add it to ebus memory region.
IMO, there is no need to add a new parameter to m48t59_init_isa device.
Tell me what do you think of it.
Hervé
next prev parent reply other threads:[~2015-01-19 22:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 11:35 [Qemu-devel] [PATCH 0/2] m48t59: add year offset and MMIO ISA mapping Mark Cave-Ayland
2015-01-19 11:35 ` [Qemu-devel] [PATCH 1/2] m48t59: introduce new year_offset qdev property Mark Cave-Ayland
2015-01-19 12:06 ` Artyom Tarasenko
2015-01-19 12:20 ` Mark Cave-Ayland
2015-01-19 11:35 ` [Qemu-devel] [PATCH 2/2] m48t59: add mem_base value to m48t59_init_isa() Mark Cave-Ayland
2015-01-19 12:45 ` Paolo Bonzini
2015-01-19 12:57 ` Artyom Tarasenko
2015-01-19 12:59 ` Paolo Bonzini
2015-01-19 13:12 ` Artyom Tarasenko
2015-01-19 15:01 ` Andreas Färber
2015-01-19 15:22 ` Artyom Tarasenko
2015-01-19 15:31 ` Paolo Bonzini
2015-01-19 15:38 ` Andreas Färber
2015-01-19 16:01 ` Paolo Bonzini
2015-01-19 16:17 ` Artyom Tarasenko
2015-01-19 16:34 ` Paolo Bonzini
2015-01-19 18:17 ` Maciej W. Rozycki
2015-01-19 16:57 ` Mark Cave-Ayland
2015-01-19 16:55 ` Mark Cave-Ayland
2015-01-19 20:03 ` Andreas Färber
2015-01-20 9:54 ` Artyom Tarasenko
2015-01-19 16:42 ` Mark Cave-Ayland
2015-01-19 21:16 ` Hervé Poussineau
2015-01-19 15:04 ` Peter Maydell
2015-01-19 16:48 ` Mark Cave-Ayland
2015-01-19 16:50 ` Peter Maydell
2015-01-19 12:09 ` [Qemu-devel] [PATCH 0/2] m48t59: add year offset and MMIO ISA mapping Artyom Tarasenko
2015-01-19 21:59 ` Hervé Poussineau [this message]
2015-01-20 10:16 ` Artyom Tarasenko
2015-01-20 14:19 ` Mark Cave-Ayland
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=54BD7E35.40108@reactos.org \
--to=hpoussin@reactos.org \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=atar4qemu@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--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).