From: Paolo Bonzini <pbonzini@redhat.com>
To: Corey Minyard <cminyard@mvista.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
Corey Minyard <minyard@acm.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] Sort the fw_cfg file list
Date: Wed, 16 Mar 2016 16:34:57 +0100 [thread overview]
Message-ID: <56E97D21.40108@redhat.com> (raw)
In-Reply-To: <56E979E3.8080806@mvista.com>
On 16/03/2016 16:21, Corey Minyard wrote:
> One more thing here. I've realized that this is used for
> non-x86, too, and I'm wondering how much those matter.
> It's going to be really hard to figure out an order for these,
> as different boards/arches use the same names and install
> them in different orders.
>
> For legacy mode, can I just put them in order for non-x86?
> Is there an easy way to detect that you are running x86?
Of all boards that support fw-cfg, only x86 does versioning so they are
not a problem.
Paolo
next prev parent reply other threads:[~2016-03-16 15:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 16:55 [Qemu-devel] [PATCH v2] Sort the fw_cfg file list minyard
2016-03-15 6:57 ` Michael S. Tsirkin
2016-03-15 7:04 ` Gerd Hoffmann
2016-03-15 7:17 ` Michael S. Tsirkin
2016-03-15 7:34 ` Gerd Hoffmann
2016-03-15 7:45 ` Michael S. Tsirkin
2016-03-15 8:45 ` Gerd Hoffmann
2016-03-15 9:37 ` Michael S. Tsirkin
2016-03-15 12:38 ` Corey Minyard
2016-03-15 12:45 ` Michael S. Tsirkin
2016-03-15 12:56 ` Corey Minyard
2016-03-15 13:47 ` Michael S. Tsirkin
2016-03-15 14:43 ` Michael S. Tsirkin
2016-03-15 16:36 ` Corey Minyard
2016-03-15 17:01 ` Michael S. Tsirkin
2016-03-16 15:21 ` Corey Minyard
2016-03-16 15:34 ` Paolo Bonzini [this message]
2016-03-16 15:37 ` Michael S. Tsirkin
2016-03-15 13:03 ` Gerd Hoffmann
2016-03-15 13:19 ` Michael S. Tsirkin
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=56E97D21.40108@redhat.com \
--to=pbonzini@redhat.com \
--cc=cminyard@mvista.com \
--cc=kraxel@redhat.com \
--cc=minyard@acm.org \
--cc=mst@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 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).