From: "Hervé Poussineau" <hpoussin@reactos.org>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 1/2] prep_pci: set isa_mem_base in the PCI host bridge
Date: Wed, 24 Jul 2013 07:37:29 +0200 [thread overview]
Message-ID: <51EF6819.5070900@reactos.org> (raw)
In-Reply-To: <51EF04A7.4080304@web.de>
Andreas Färber a écrit :
> Am 23.07.2013 23:16, schrieb Hervé Poussineau:
>> Currently, it is done by i82378 device, which shouldn't care of it.
>>
>> Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
>> ---
>> hw/isa/i82378.c | 3 ---
>> hw/pci-host/prep.c | 2 ++
>> 2 files changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/hw/isa/i82378.c b/hw/isa/i82378.c
>> index b25ed04..de71d81 100644
>> --- a/hw/isa/i82378.c
>> +++ b/hw/isa/i82378.c
>> @@ -45,7 +45,6 @@ typedef struct I82378State {
>> typedef struct PCIi82378State {
>> PCIDevice pci_dev;
>> uint32_t isa_io_base;
>> - uint32_t isa_mem_base;
>> I82378State state;
>> } PCIi82378State;
>>
>> @@ -234,7 +233,6 @@ static int pci_i82378_init(PCIDevice *dev)
>> pci_set_long(dev->wmask + PCI_BASE_ADDRESS_0, 0);
>> pci_set_long(pci_conf + PCI_BASE_ADDRESS_0, pci->isa_io_base);
>>
>> - isa_mem_base = pci->isa_mem_base;
>> isa_bus_new(&dev->qdev, pci_address_space_io(dev));
>>
>> i82378_init(&dev->qdev, s);
>> @@ -244,7 +242,6 @@ static int pci_i82378_init(PCIDevice *dev)
>>
>> static Property i82378_properties[] = {
>> DEFINE_PROP_HEX32("iobase", PCIi82378State, isa_io_base, 0x80000000),
>> - DEFINE_PROP_HEX32("membase", PCIi82378State, isa_mem_base, 0xc0000000),
>> DEFINE_PROP_END_OF_LIST()
>> };
>>
>> diff --git a/hw/pci-host/prep.c b/hw/pci-host/prep.c
>> index b41d564..d6bcc63 100644
>> --- a/hw/pci-host/prep.c
>> +++ b/hw/pci-host/prep.c
>> @@ -119,6 +119,8 @@ static void raven_pcihost_realizefn(DeviceState *d, Error **errp)
>> MemoryRegion *address_space_mem = get_system_memory();
>> int i;
>>
>> + isa_mem_base = 0xc0000000;
>> +
>> for (i = 0; i < 4; i++) {
>> sysbus_init_irq(dev, &s->irq[i]);
>> }
>
> Patch is okay with me, but I wonder what we still need the global
> isa_mem_base for? The only users seem to be VGA, adding offsets to it.
Indeed, isa_mem_base should be removed, and PCI bus regions (memory and
I/O) should be adapted in PCI host.
However, while I have a patch pending, it is not ready yet, so I prefer
to postpone it past QEMU 1.6.
Hervé
next prev parent reply other threads:[~2013-07-24 5:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 21:16 [Qemu-devel] [PATCH 0/2] prep/i82378: simplify and enhance i82378 chipset implementation Hervé Poussineau
2013-07-23 21:16 ` [Qemu-devel] [PATCH 1/2] prep_pci: set isa_mem_base in the PCI host bridge Hervé Poussineau
2013-07-23 22:33 ` Andreas Färber
2013-07-24 5:37 ` Hervé Poussineau [this message]
2013-07-23 21:16 ` [Qemu-devel] [PATCH 2/2] i82378: cleanup implementation Hervé Poussineau
2013-07-29 21:53 ` Andreas Färber
2013-07-30 20:06 ` Hervé Poussineau
2013-07-31 17:06 ` Andreas Färber
2013-07-31 17:23 ` Andreas Färber
2013-07-31 18:58 ` Hervé Poussineau
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=51EF6819.5070900@reactos.org \
--to=hpoussin@reactos.org \
--cc=agraf@suse.de \
--cc=andreas.faerber@web.de \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--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).