From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>
Subject: [Qemu-devel] [PATCH v3 for-1.6 0/3] Remove legacy sysfw code
Date: Fri, 9 Aug 2013 12:34:59 -0500 [thread overview]
Message-ID: <1376069702-22330-1-git-send-email-aliguori@us.ibm.com> (raw)
Paolo's cover letter for v2:
The sysfw code to choose between ROM and flash BIOS was a bad idea,
because it triggered different behavior between TCG and KVM. We
deleted the behavior in 1.5, but we left the code around because
it was close to the release. Now it's time to delete it.
v1->v2 only changes commit messages.
My own remarks for v3:
I just noticed this still hasn't been applied. I want it in 1.6,
because it cleans up a partially new public interface. v2 doesn't
apply anymore after being left to rot for two months, so I rebased it.
Paolo Bonzini (3):
sysfw: remove read-only pc_sysfw_flash_vs_rom_bug_compatible
pc_sysfw: remove the rom_only property
pc_sysfw: do not make it a device anymore
default-configs/i386-softmmu.mak | 1 -
default-configs/x86_64-softmmu.mak | 1 -
hw/block/Makefile.objs | 1 -
hw/i386/Makefile.objs | 1 +
hw/i386/pc.c | 2 +-
hw/i386/pc_piix.c | 15 +---
hw/i386/pc_q35.c | 1 +
hw/{block => i386}/pc_sysfw.c | 136 +++----------------------------------
include/hw/i386/pc.h | 4 +-
9 files changed, 15 insertions(+), 147 deletions(-)
rename hw/{block => i386}/pc_sysfw.c (62%)
--
1.7.11.7
next reply other threads:[~2013-08-09 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 17:34 Anthony Liguori [this message]
2013-08-09 17:35 ` [Qemu-devel] [PATCH v3 1/3] sysfw: remove read-only pc_sysfw_flash_vs_rom_bug_compatible Anthony Liguori
2013-08-09 17:35 ` [Qemu-devel] [PATCH v3 2/3] pc_sysfw: remove the rom_only property Anthony Liguori
2013-08-09 17:35 ` [Qemu-devel] [PATCH v3 3/3] pc_sysfw: do not make it a device anymore Anthony Liguori
2013-08-09 17:52 ` [Qemu-devel] [PATCH v3 for-1.6 0/3] Remove legacy sysfw code Markus Armbruster
2013-08-14 16:27 ` Anthony Liguori
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=1376069702-22330-1-git-send-email-aliguori@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.