From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org, seabios@seabios.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PATCH 0/4] qemu option loading
Date: Fri, 18 Dec 2009 12:16:00 +0100 [thread overview]
Message-ID: <1261134964-12427-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
qemu is about to change the way how option roms are loaded. pci roms
will be loaded into a option rom bar (like real hardware does).
non-pci roms can be loaded using the qemu firmware interface.
With this change seabios will deploy all roms instead of having qemu
copy them to the 0xc0000 -> 0e0000 range. Advantages are:
* roms can be packed better, especially in case they resize themself
(like the gPXE roms do).
* rom area is a bit larger as seabios can additionally use the
unused regions of the 0xe0000 segment.
* the whole process comes closer to what happens on real hardware.
cheers,
Gerd
next reply other threads:[~2009-12-18 11:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 11:16 Gerd Hoffmann [this message]
2009-12-18 11:16 ` [Qemu-devel] [PATCH 1/4] Do not guard qemu shadow ram work around in CONFIG_OPTIONROMS_DEPLOYED Gerd Hoffmann
2009-12-18 11:16 ` [Qemu-devel] [PATCH 2/4] Disable CONFIG_OPTIONROMS_DEPLOYED by default Gerd Hoffmann
2009-12-18 11:16 ` [Qemu-devel] [PATCH 3/4] move htonl() + friends to util.h Gerd Hoffmann
2009-12-18 11:16 ` [Qemu-devel] [PATCH 4/4] qemu: add rom loading via fw_cfg Gerd Hoffmann
2009-12-18 15:41 ` [Qemu-devel] Re: [SeaBIOS] [PATCH 0/4] qemu option loading Anthony Liguori
2009-12-18 15:52 ` Gerd Hoffmann
2009-12-18 16:22 ` Anthony Liguori
2009-12-18 16:37 ` Gerd Hoffmann
2009-12-18 23:40 ` Kevin O'Connor
2009-12-19 0:37 ` Kevin O'Connor
2009-12-19 2:55 ` Anthony Liguori
2009-12-19 3:37 ` Kevin O'Connor
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=1261134964-12427-1-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).