From: Paolo Bonzini <pbonzini@redhat.com>
To: Artyom Tarasenko <atar4qemu@gmail.com>
Cc: qemu-ppc@nongnu.org,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
qemu-devel <qemu-devel@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>,
"Alexander Graf" <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 2/2] m48t59: add mem_base value to m48t59_init_isa()
Date: Mon, 19 Jan 2015 13:59:38 +0100 [thread overview]
Message-ID: <54BCFFBA.1070302@redhat.com> (raw)
In-Reply-To: <CACXAS8Di2q=YMU+1MviCxM9SPYr=Fii=20LCqJUOgD_=p7=Tfw@mail.gmail.com>
On 19/01/2015 13:57, Artyom Tarasenko wrote:
>> > Is it really ISA if it's MMIO? In other words, why can't this be a
>> > sysbus device?
> On physical machines it's EBus, which is pretty much like 8-bit ISA.
> So, I think modelling it as ISA is closer to to the reality.
> But out of curiosity, would it be possible to have a sysbus device
> somewhere in a middle of PCI space? Do sysbus devices have higher
> priority if the address spaces overlap? Or do you mean that the PCI
> controller needs to be modified to have a hole for a sysbus device?
What does the memory map look like (simplifying to "where can BARs be"
and "where is the RTC")?
Paolo
next prev parent reply other threads:[~2015-01-19 12:59 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 [this message]
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
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=54BCFFBA.1070302@redhat.com \
--to=pbonzini@redhat.com \
--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 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.