From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Avi Kivity <avi@redhat.com>,
qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] Re: [PATCH] write option roms in pc-bios/
Date: Fri, 08 Jan 2010 06:29:14 -0600 [thread overview]
Message-ID: <4B47251A.10300@linux.vnet.ibm.com> (raw)
In-Reply-To: <4B46DF6D.7060306@redhat.com>
On 01/08/2010 01:31 AM, Paolo Bonzini wrote:
> On 01/07/2010 09:03 PM, Anthony Liguori wrote:
>>
>> This will wreak havoc on the tree since these are built by default and
>> they are replacing files in revision control.
>
> ... the next question is why are they (linuxboot.bin and
> multiboot.bin) in revision control since they do not require any
> strange tool to be built.
If you're just thinking about x86 and kvm, sure, but when you consider a
default build creates tcg targets for arm, sparc, mips, etc, and that
they all need firmware, it's extremely unlikely that any given user has
all of the cross compilers available to build all of the roms.
Yes, we could and should be smarter about building roms when we can and
making sure we install and use those whenever possible. We still need
to ship roms though for the foreseeable future.
Regards,
Anthony Liguori
> Paolo
next prev parent reply other threads:[~2010-01-08 12:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B337318.6080901@redhat.com>
[not found] ` <1261664861-15493-1-git-send-email-pbonzini@redhat.com>
2010-01-07 20:03 ` [Qemu-devel] [PATCH] write option roms in pc-bios/ Anthony Liguori
2010-01-08 7:31 ` [Qemu-devel] " Paolo Bonzini
2010-01-08 7:57 ` Aurelien Jarno
2010-01-08 8:19 ` Paolo Bonzini
2010-01-08 9:12 ` Aurelien Jarno
2010-01-08 12:29 ` Anthony Liguori [this message]
[not found] <668989114.432161262946223474.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2010-01-08 10:26 ` Paolo Bonzini
2010-01-08 17:54 ` Blue Swirl
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=4B47251A.10300@linux.vnet.ibm.com \
--to=aliguori@linux.vnet.ibm.com \
--cc=avi@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).