From: Paolo Bonzini <pbonzini@redhat.com>
To: Jordan Justen <jljusten@gmail.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>,
qemu-devel <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/3] pc_sysfw: remove the rom_only property
Date: Mon, 03 Jun 2013 23:00:02 +0200 [thread overview]
Message-ID: <51AD03D2.6080905@redhat.com> (raw)
In-Reply-To: <CAFe8ug9mU_+0sOGVwQfv_Rt=kRgf8-p2Yhfdwr+Ps467AGEd_A@mail.gmail.com>
Il 03/06/2013 22:50, Jordan Justen ha scritto:
> On Mon, Jun 3, 2013 at 8:19 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> > With the new semantics of pc_sysfw (no -pflash implies "old-style" ROM setup,
>> > -pflash implies "new-style" ROM setup), there is no need anymore for a compat
>> > property. Old machines simply will never use -pflash, and thus will always
>> > use old-style setup.
> QEMU 1.2-1.5 could use -pflash if kvm was not used.
"Old machines" actually referred to <=1.0. This patch will not break
backwards compatibility with QEMU 1.2-1.5 as long as you always use -pflash.
Paolo
next prev parent reply other threads:[~2013-06-03 21:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 15:19 [Qemu-devel] [PATCH 0/3] Remove legacy sysfw code Paolo Bonzini
2013-06-03 15:19 ` [Qemu-devel] [PATCH 1/3] sysfw: remove read-only pc_sysfw_flash_vs_rom_bug_compatible Paolo Bonzini
2013-06-03 20:36 ` Jordan Justen
2013-06-03 20:57 ` Paolo Bonzini
2013-06-04 9:17 ` Markus Armbruster
2013-06-04 9:14 ` Markus Armbruster
2013-06-04 9:43 ` Paolo Bonzini
2013-06-03 15:19 ` [Qemu-devel] [PATCH 2/3] pc_sysfw: remove the rom_only property Paolo Bonzini
2013-06-03 20:50 ` Jordan Justen
2013-06-03 21:00 ` Paolo Bonzini [this message]
2013-06-03 15:19 ` [Qemu-devel] [PATCH 3/3] pc_sysfw: do not make it a device anymore Paolo Bonzini
2013-06-03 20:46 ` Jordan Justen
2013-06-03 21:00 ` Paolo Bonzini
2013-06-03 21:56 ` [Qemu-devel] [PATCH 0/3] Remove legacy sysfw code Jordan Justen
2013-06-04 6:46 ` Paolo Bonzini
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=51AD03D2.6080905@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=jljusten@gmail.com \
--cc=jordan.l.justen@intel.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 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).