qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] docs: add firmware.txt
Date: Wed, 4 Jul 2018 17:44:07 -0300	[thread overview]
Message-ID: <20180704204407.GA22336@localhost.localdomain> (raw)
In-Reply-To: <20170901105331.11783-1-kraxel@redhat.com>

On Fri, Sep 01, 2017 at 12:53:31PM +0200, Gerd Hoffmann wrote:
> Document how guest firmware is handled in qemu today.
> 
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>

Is this document still valid?  Should we apply this for QEMU 3.0?

> ---
>  docs/firmware.txt | 49 +++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 49 insertions(+)
>  create mode 100644 docs/firmware.txt
> 
> diff --git a/docs/firmware.txt b/docs/firmware.txt
> new file mode 100644
> index 0000000000..e242413344
> --- /dev/null
> +++ b/docs/firmware.txt
> @@ -0,0 +1,49 @@
> +
> +prebuilt firmware in qemu
> +=========================
> +
> +The process of building firmware isn't as easy as building qemu
> +itself, for example because you must have cross compilers installed
> +when building firmware for other architectures.  So qemu ships
> +prebuilt firmware binaries for convenience reasons.
> +
> +
> +directories
> +-----------
> +
> +pc-bios/
> +    Firmware binaries.
> +    Also other files like keymaps and logos which are copied to
> +    $prefix/share/qemu by "make install".
> +
> +pc-bios/optionrom/
> +    Firmware sources, part of the qemu project.
> +
> +roms/
> +    Firmware sources, third-party projects, as git submodules.
> +
> +
> +third-party git repos
> +---------------------
> +
> +For third party firmware sources it is recommended to have a git
> +mirror on git.qemu.org.  In case the firmware license is GPL the git
> +mirror is mandatory for GPL compilance reasons:  We ship binaries, so
> +we must provide sources too.
> +
> +
> +building the firmware
> +---------------------
> +
> +Firmware builds should be done using rules in roms/Makefile.  That
> +serves as documentation how the firmware is built, and it also makes
> +firmware updates easier for the maintainer.
> +
> +"make -C roms" prints a list of firmware build targets.
> +"make -C roms $target" kicks a build.
> +
> +
> +notes for specific firmwares
> +----------------------------
> +
> +ipxe: see https://wiki.qemu.org/IpxeDownstreamForQemu
> -- 
> 2.9.3
> 
> 

-- 
Eduardo

  reply	other threads:[~2018-07-04 20:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 10:53 [Qemu-devel] [PATCH] docs: add firmware.txt Gerd Hoffmann
2018-07-04 20:44 ` Eduardo Habkost [this message]
2018-07-05  6:47   ` 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=20180704204407.GA22336@localhost.localdomain \
    --to=ehabkost@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).