From: "Daniel P. Berrange" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/1] qemu-firmware repo
Date: Wed, 27 Sep 2017 10:15:31 +0100 [thread overview]
Message-ID: <20170927091531.GA12223@redhat.com> (raw)
In-Reply-To: <7f50b7bb-bbf7-7e0e-754a-234d4244fb72@redhat.com>
On Wed, Sep 27, 2017 at 09:19:22AM +0200, Paolo Bonzini wrote:
> On 26/09/2017 13:17, Gerd Hoffmann wrote:
> >
> > Ok, we want for varios reasons separate the firmware from the main
> > qemu repo. Here is my attempt to create such a repo. For starters
> > only seabios has been added here.
> >
> > You can find the repo with currently three patches here:
> > https://www.kraxel.org/cgit/qemu-firmware/
> >
> > This "series" is only patch #2 of the repo. Havn't found a way to
> > convince git-format-patch to include the initial commit of a repo.
> > But patch #1 (the initial commit) only adds the seabios submodule,
> > patch #3 adds the binary blobs, so patch #2 actually is the most
> > interesting one.
>
> Are you planning to include only submodules, or also "QEMU-native"
> firmware such as linuxboot, kvmvapic, s390-ccw, spapr-rtas, etc.?
The submodules make sense to split out because distro vendors buld them
independently of QEMU, and would rather not have them in the tarballs,
so they have a clearer path to license compliance and legal export
certification.
The other bits of mention are all built normally as part of QEMU and
not subject to these problems, so I don't see a benefit to splitting
them out of QEMU. In fact putting those bits in the qemu-firmware
repo would re-introduce the problem we're trying to solve because
distros would then need to get linuxboox, kvmvapi etc from a tarball
of qemu-firmware which would once again include all the bits they
don't want to have.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-09-27 9:15 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 [this message]
2017-09-27 10:45 ` Gerd Hoffmann
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=20170927091531.GA12223@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@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 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.