From: Paolo Bonzini <pbonzini@redhat.com>
To: Artyom Tarasenko <atar4qemu@gmail.com>
Cc: "Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Alexander Graf" <agraf@suse.de>,
qemu-devel <qemu-devel@nongnu.org>,
qemu-ppc@nongnu.org, "Hervé Poussineau" <hpoussin@reactos.org>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH 2/2] m48t59: add mem_base value to m48t59_init_isa()
Date: Mon, 19 Jan 2015 17:34:28 +0100 [thread overview]
Message-ID: <54BD3214.4060209@redhat.com> (raw)
In-Reply-To: <CACXAS8CYA=HUuThp2fFLtWMOHGJQu_ZQzoVvvFs0KfvaXhhniA@mail.gmail.com>
On 19/01/2015 17:17, Artyom Tarasenko wrote:
> On Mon, Jan 19, 2015 at 4:31 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>>
>> On 19/01/2015 16:22, Artyom Tarasenko wrote:
>>>>>>>
>>>>>>> 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? [...]
>>>>>
>>>>> Why would you want to use a SysBusDevice in the first place?
>>> Ask Paolo. :-) For me it's only important to have a MMIO device in the
>>> proper address range.
>>
>> The reason I asked is simply because ISA devices never do MMIO (apart
>> for the VGA window).
>
> You mean in the QEMU world? At least physical SCSI and Ethernet
> adapters had a MMIO space for the onboard ROM.
Uh right, ROMs count as MMIO too.
>>>>> I previously discussed with Mark that it should be an EBusDevice, not an
>>>>> ISADevice or SysBusDevice.
>>> Interesting. I can't find this discussion in the list archive. Do you suggest to
>>> create EBusDevices for all ISA devices (serial, parallel, keyboard,
>>> floppy) used in sun4u, or only for m48t59?
>>> What would be the advantage of using EBusDevice over ISADevice?
>>
>> Is there a description of EBus and the sun4u memory map somewhere?
>
> I could find only sparse pieces. "Uniprocessor System Controller
> User's Manual" (805-0170.pdf) has some brief description, it's also
> mentioned in the STP2223BGA and STP2200ABGA data sheets.
>
>> Is there an "EBus bridge" PCI device similar to the PCI-to-ISA bridge?
>
> As physical devices there are integrated SBus-to-EBus and PCI-to-EBus bridges.
>
> But actually I may have been wrong about NVRAM always sitting on the
> EBus: looking at the page 28 of "UltraSPARC™-IIi User's Manual"
> (805-0087.pdf), I see that NVRAM, Serial and other controllers reside
> in a "PC compatible SuperIO" chip which sits on a PCI bus.
That's an ISA bridge basically. I understand a little more of how this
is supposed to work now, but I think it makes little sense to add this
patch without the corresponding user.
Paolo
next prev parent reply other threads:[~2015-01-19 16:35 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 [this message]
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=54BD3214.4060209@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=atar4qemu@gmail.com \
--cc=hpoussin@reactos.org \
--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.