Re: [Qemu-devel] [PATCH 2/2] m48t59: add mem_base value to m48t59_init_isa()

From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>,
	"Artyom Tarasenko" <atar4qemu@gmail.com>
Cc: qemu-ppc@nongnu.org, "Hervé Poussineau" <hpoussin@reactos.org>,
	"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
	qemu-devel <qemu-devel@nongnu.org>,
	"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 17:01:08 +0100	[thread overview]
Message-ID: <54BD2A44.9020901@redhat.com> (raw)
In-Reply-To: <54BD24F5.70309@suse.de>

On 19/01/2015 16:38, Andreas Färber wrote:
>> > Is there an "EBus bridge" PCI device similar to the PCI-to-ISA bridge?
> In the previous dump, the "ebus" entry looked like one to me?
> 
>     bus: pci
>       dev: ebus, id ""
>         addr = 03.0
>         class Bridge, addr 00:03.0, pci id 108e:1000 (sub 1af4:1100)
>         bar 0: mem at 0x3000000 [0x3ffffff]
>         bar 1: i/o at 0x4000 [0x7fff]
>         bus: isa.0
>           type ISA
> 
> Confusingly named, as "ebus" would be a better type name for the actual
> bus, but "EBus" might work as bus name if we actually need one (does the
> user add devices to this bus or are these all chipset features
> recursively set up by the machine?). Otherwise they could just be
> child<> properties on the ebus device.

So is this m48t59 device mapped inside a BAR of its parent ebus device?

What value will the sun4u patch pass for mem_base?

Paolo