From: Andre Przywara <andre.przywara@amd.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] add missing firmware configuration channel numbers to BIOS
Date: Mon, 22 Dec 2008 00:49:35 +0100 [thread overview]
Message-ID: <494ED60F.6000509@amd.com> (raw)
Hi,
although we currently don't use firmware config channel
numbers higher than '0x02' in the PC-BIOS, add the channel
names to the BIOS source to mark already used entries.
This will make picking new number easier in the future.
Signed-off-by: Andre Przywara <andre.przywara@amd.com>
Regards,
Andre.
---
From: Andre Przywara <andre.przywara@amd.com>
sync firmware configuration channel numbers between QEMU and BIOS
diff --git a/pc-bios/bios-pq/0006_fw_cfg_sync.patch b/pc-bios/bios-pq/0006_fw_cfg_sync.patch
new file mode 100644
index 0000000..9f958c0
--- /dev/null
+++ b/pc-bios/bios-pq/0006_fw_cfg_sync.patch
@@ -0,0 +1,19 @@
+From: Andre Przywara <andre.przywara@amd.com>
+
+ add missing qemu firmware configuration inferface channel numbers
+
+diff --git a/bios/rombios32.c b/bios/rombios32.c
+index f81b269..3d42528 100644
+--- a/bios/rombios32.c
++++ b/bios/rombios32.c
+@@ -413,6 +413,10 @@ unsigned long bios_table_end_addr;
+ #define QEMU_CFG_SIGNATURE 0x00
+ #define QEMU_CFG_ID 0x01
+ #define QEMU_CFG_UUID 0x02
++#define QEMU_CFG_RAM_SIZE 0x03
++#define QEMU_CFG_NOGRAPHIC 0x04
++#define QEMU_CFG_NB_CPUS 0x05
++#define QEMU_CFG_MACHINE_ID 0x06
+
+ int qemu_cfg_port;
+
diff --git a/pc-bios/bios-pq/series b/pc-bios/bios-pq/series
index 0e7558c..bf40a88 100644
--- a/pc-bios/bios-pq/series
+++ b/pc-bios/bios-pq/series
@@ -2,3 +2,4 @@
0002_e820-high-mem.patch
0003_smp-startup-poll.patch
0005_hpet.patch
+0006_fw_cfg_sync.patch
next reply other threads:[~2008-12-21 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 23:49 Andre Przywara [this message]
2008-12-22 6:29 ` [Qemu-devel] [PATCH] add missing firmware configuration channel numbers to BIOS Blue Swirl
2008-12-22 9:36 ` Andre Przywara
2008-12-22 10:34 ` Blue Swirl
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=494ED60F.6000509@amd.com \
--to=andre.przywara@amd.com \
--cc=anthony@codemonkey.ws \
--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).