From: Artyom Tarasenko <atar4qemu@gmail.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: "Hervé Poussineau" <hpoussin@reactos.org>,
"Andreas Färber" <andreas.faerber@web.de>,
qemu-ppc@nongnu.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3 09/10] raven: fix PCI bus accesses with size > 1
Date: Sun, 16 Mar 2014 23:27:43 +0100 [thread overview]
Message-ID: <CACXAS8CjzpbLHYyHvj32fzZhMgPSVwxbMxtXar6OsP1Joi6HSg@mail.gmail.com> (raw)
In-Reply-To: <CACXAS8DhoVkSweZ0WiOYOY-phB223Rsdw2WHQ0ULPAuVW0umcA@mail.gmail.com>
Hi Andreas, Hervé,
this patch seems still be missing in master. Is it causing any problems?
Artyom
On Mon, Feb 10, 2014 at 11:46 PM, Artyom Tarasenko <atar4qemu@gmail.com> wrote:
> On Tue, Nov 5, 2013 at 12:09 AM, Hervé Poussineau <hpoussin@reactos.org> wrote:
>> Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
>
> Without this patch PReP is broken really bad. Was going to submit the
> same fix, and then found that the bug was already fixed 4 months ago.
>
> Hope it helps getting it closer to master:
>
> Tested-by: Artyom Tarasenko <atar4qemu@gmail.com>
>
>> ---
>> hw/pci-host/prep.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/hw/pci-host/prep.c b/hw/pci-host/prep.c
>> index c11679a..4eabe31 100644
>> --- a/hw/pci-host/prep.c
>> +++ b/hw/pci-host/prep.c
>> @@ -222,12 +222,12 @@ static void raven_pcihost_realizefn(DeviceState *d, Error **errp)
>>
>> pci_bus_irqs(&s->pci_bus, prep_set_irq, prep_map_irq, s->irq, PCI_NUM_PINS);
>>
>> - memory_region_init_io(&h->conf_mem, OBJECT(h), &pci_host_conf_be_ops, s,
>> - "pci-conf-idx", 1);
>> + memory_region_init_io(&h->conf_mem, OBJECT(h), &pci_host_conf_le_ops, s,
>> + "pci-conf-idx", 4);
>> memory_region_add_subregion(&s->pci_io, 0xcf8, &h->conf_mem);
>>
>> - memory_region_init_io(&h->data_mem, OBJECT(h), &pci_host_data_be_ops, s,
>> - "pci-conf-data", 1);
>> + memory_region_init_io(&h->data_mem, OBJECT(h), &pci_host_data_le_ops, s,
>> + "pci-conf-data", 4);
>> memory_region_add_subregion(&s->pci_io, 0xcfc, &h->data_mem);
>>
>> memory_region_init_io(&h->mmcfg, OBJECT(s), &PPC_PCIIO_ops, s, "pciio", 0x00400000);
next prev parent reply other threads:[~2014-03-16 22:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 22:46 [Qemu-devel] [PATCH v3 09/10] raven: fix PCI bus accesses with size > 1 Artyom Tarasenko
2014-02-10 22:55 ` [Qemu-devel] [Qemu-ppc] " Mark Cave-Ayland
2014-02-11 23:32 ` Andreas Färber
2014-03-16 22:27 ` Artyom Tarasenko [this message]
2014-03-17 19:59 ` [Qemu-devel] " Andreas Färber
2014-03-17 21:55 ` Artyom Tarasenko
2014-03-17 22:25 ` Hervé Poussineau
2014-03-19 22:44 ` Andreas Färber
2014-03-17 22:28 ` Mark Cave-Ayland
2014-03-19 22:47 ` Andreas Färber
-- strict thread matches above, loose matches on Subject: below --
2013-11-04 23:09 [Qemu-devel] [PATCH v3 00/10] prep: improve Raven PCI host emulation Hervé Poussineau
2013-11-04 23:09 ` [Qemu-devel] [PATCH v3 09/10] raven: fix PCI bus accesses with size > 1 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=CACXAS8CjzpbLHYyHvj32fzZhMgPSVwxbMxtXar6OsP1Joi6HSg@mail.gmail.com \
--to=atar4qemu@gmail.com \
--cc=afaerber@suse.de \
--cc=andreas.faerber@web.de \
--cc=hpoussin@reactos.org \
--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).