From: Gerd Hoffmann <kraxel@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/1] qemu-firmware repo
Date: Wed, 27 Sep 2017 12:45:36 +0200 [thread overview]
Message-ID: <1506509136.25036.7.camel@redhat.com> (raw)
In-Reply-To: <20170927091531.GA12223@redhat.com>
Hi,
> The other bits of mention are all built normally as part of QEMU and
> not subject to these problems,
Sure? As far I know no firmware is build automatically as cross
compilers might be needed to do that for guest arch != host arch.
But yes, we don't have licensing issues (we ship the sources too),
so keeping them in the main repo isn't that a big issue.
cheers,
Gerd
next prev parent reply other threads:[~2017-09-27 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 11:17 [Qemu-devel] [PATCH 0/1] qemu-firmware repo Gerd Hoffmann
2017-09-26 11:17 ` [Qemu-devel] [PATCH 1/1] add Makefile, add configs for seabios Gerd Hoffmann
2017-09-27 7:19 ` [Qemu-devel] [PATCH 0/1] qemu-firmware repo Paolo Bonzini
2017-09-27 9:11 ` Gerd Hoffmann
2017-09-27 9:15 ` Daniel P. Berrange
2017-09-27 10:45 ` Gerd Hoffmann [this message]
2017-09-27 11:34 ` Paolo Bonzini
2017-09-27 12:01 ` Daniel P. Berrange
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=1506509136.25036.7.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@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).