qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [RfC PATCH 0/3] edk2: add efi firmware builds
Date: Wed, 23 Nov 2016 14:24:41 +0100	[thread overview]
Message-ID: <1479907484-4988-1-git-send-email-kraxel@redhat.com> (raw)

  Hi,

This patch series adds a edk2 submodule in roms, also a build script
and makefile rules to build ovmf and arm firmware.

The build script creates per-arch subdirs in pc-bios and places the
firmware files there.  They are not exactly small:

   kraxel@nilsson ~/projects/qemu (work/edk2)# du -s -h pc-bios/edk2-*
   2,8M    pc-bios/edk2-aarch64
   2,8M    pc-bios/edk2-arm
   2,1M    pc-bios/edk2-i386
   2,1M    pc-bios/edk2-x86_64

So, the question is how we wanna go forward with this.  Adding the
submodule and rules is a no-brainer I think.  But what about the
binaries, which sum up to roughly 10M?  Ship them all?  Ship the
64bit archs only, given that efi never really took off on i386
and arm?

Other comments?

cheers,
  Gerd

Gerd Hoffmann (3):
  edk2: add submodule
  edk2: add build script and rules
  edk2: use EfiRom utility from edk2 submodule

 .gitmodules          |  3 +++
 roms/Makefile        | 50 ++++++++++++++++++++++++++++++--------------
 roms/compile-edk2.sh | 59 ++++++++++++++++++++++++++++++++++++++++++++++++++++
 roms/edk2            |  1 +
 4 files changed, 97 insertions(+), 16 deletions(-)
 create mode 100755 roms/compile-edk2.sh
 create mode 160000 roms/edk2

-- 
1.8.3.1

             reply	other threads:[~2016-11-23 13:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23 13:24 Gerd Hoffmann [this message]
2016-11-23 13:24 ` [Qemu-devel] [RfC PATCH 1/3] edk2: add submodule Gerd Hoffmann
2016-11-23 13:24 ` [Qemu-devel] [RfC PATCH 2/3] edk2: add build script and rules Gerd Hoffmann
2016-11-23 13:24 ` [Qemu-devel] [RfC PATCH 3/3] edk2: use EfiRom utility from edk2 submodule Gerd Hoffmann
2016-11-23 14:54 ` [Qemu-devel] [RfC PATCH 0/3] edk2: add efi firmware builds Daniel P. Berrange
2016-11-28 10:07   ` Gerd Hoffmann

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=1479907484-4988-1-git-send-email-kraxel@redhat.com \
    --to=kraxel@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).