From: "Hervé Poussineau" <hpoussin@reactos.org>
To: qemu-devel@nongnu.org
Cc: "Andreas Färber" <andreas.faerber@web.de>, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/2] prep: Remove some clearly wrong assumptions
Date: Tue, 20 May 2014 07:34:44 +0200 [thread overview]
Message-ID: <537AE974.6090108@reactos.org> (raw)
In-Reply-To: <1398287975-14684-1-git-send-email-hpoussin@reactos.org>
Ping.
Le 23/04/2014 23:19, Hervé Poussineau a écrit :
> Hi,
>
> These two patches remove some bugs for a PReP firmware. Note that first patch is very
> PReP-oriented, and breaks OHW compatibility with other QEMU emulations (oldworld and
> newworld machines).
> Patches to remove corresponding hacks on QEMU side have already been sent:
> http://lists.gnu.org/archive/html/qemu-devel/2014-04/msg00240.html
>
> Hervé
>
> Changes v1 -> v2:
> - rewrite patch 2 as suggested by Alexander Graf
>
> Hervé Poussineau (2):
> ohw: correctly program BAR addresses of PCI devices
> ohw: let the right reset entry point 0xfff00100 jump to the currently
> wrong entry point (0xfffffffc)
>
> src/pci.c | 7 ++++++-
> src/vectors.S | 4 +++-
> 2 files changed, 9 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2014-05-20 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1398287975-14684-1-git-send-email-hpoussin@reactos.org>
[not found] ` <1398287975-14684-3-git-send-email-hpoussin@reactos.org>
2014-05-02 10:06 ` [Qemu-devel] [Qemu-ppc] [PATCH v2 2/2] ohw: let the right reset entry point 0xfff00100 jump to the currently wrong entry point (0xfffffffc) Alexander Graf
2014-05-20 5:34 ` Hervé Poussineau [this message]
[not found] ` <5384E01E.8020608@reactos.org>
[not found] ` <53851E00.1010603@suse.de>
[not found] ` <53851E84.80003@suse.de>
2014-06-15 14:31 ` [Qemu-devel] [Qemu-ppc] [PATCH v2 0/2] prep: Remove some clearly wrong assumptions Hervé Poussineau
2014-06-27 15:11 ` 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=537AE974.6090108@reactos.org \
--to=hpoussin@reactos.org \
--cc=andreas.faerber@web.de \
--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).