From: "Andreas Färber" <andreas.faerber@web.de>
To: "Hervé Poussineau" <hpoussin@reactos.org>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 4/7] raven: set a correct PCI memory region
Date: Thu, 20 Mar 2014 00:24:26 +0100 [thread overview]
Message-ID: <532A272A.3000202@web.de> (raw)
In-Reply-To: <1395093625-17470-5-git-send-email-hpoussin@reactos.org>
Am 17.03.2014 23:00, schrieb Hervé Poussineau:
> PCI memory region is 0x3f000000 bytes starting at 0xc0000000.
>
> However, keep compatibility with Open Hack'Ware expectations
> by adding a hack for Open Hack'Ware display.
Have you taken a look whether we can fix this on the OHW side? I don't
feel we need to be compatible with arbitrary OHW versions, so getting
the two hacks out would be nice as follow-up.
Regards,
Andreas
next prev parent reply other threads:[~2014-03-19 23:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 22:00 [Qemu-devel] [PATCH v4 0/7] prep: improve Raven PCI host emulation Hervé Poussineau
2014-03-17 22:00 ` [Qemu-devel] [PATCH v4 1/7] raven: rename intack region to pci_intack Hervé Poussineau
2014-03-17 22:00 ` [Qemu-devel] [PATCH v4 2/7] raven: implement non-contiguous I/O region Hervé Poussineau
2014-03-19 23:22 ` Andreas Färber
2014-03-17 22:00 ` [Qemu-devel] [PATCH v4 3/7] raven: set a correct PCI I/O memory region Hervé Poussineau
2014-03-17 22:00 ` [Qemu-devel] [PATCH v4 4/7] raven: set a correct PCI " Hervé Poussineau
2014-03-19 23:24 ` Andreas Färber [this message]
2014-03-17 22:00 ` [Qemu-devel] [PATCH v4 5/7] raven: add PCI bus mastering address space Hervé Poussineau
2014-03-17 22:00 ` [Qemu-devel] [PATCH v4 6/7] raven: fix PCI bus accesses with size > 1 Hervé Poussineau
2014-03-18 9:23 ` Artyom Tarasenko
2014-03-17 22:00 ` [Qemu-devel] [PATCH v4 7/7] raven: use raven_ for all function prefixes 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=532A272A.3000202@web.de \
--to=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).