From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [6738] Sparse fixes: move ACPI table definitions to pc.h
Date: Sat, 07 Mar 2009 15:50:18 +0000 [thread overview]
Message-ID: <E1Lfyn4-0007qJ-Uk@cvs.savannah.gnu.org> (raw)
Revision: 6738
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6738
Author: blueswir1
Date: 2009-03-07 15:50:18 +0000 (Sat, 07 Mar 2009)
Log Message:
-----------
Sparse fixes: move ACPI table definitions to pc.h
Modified Paths:
--------------
trunk/hw/pc.c
trunk/hw/pc.h
Modified: trunk/hw/pc.c
===================================================================
--- trunk/hw/pc.c 2009-03-07 15:46:23 UTC (rev 6737)
+++ trunk/hw/pc.c 2009-03-07 15:50:18 UTC (rev 6738)
@@ -54,9 +54,6 @@
#define MAX_IDE_BUS 2
-extern uint8_t *acpi_tables;
-extern size_t acpi_tables_len;
-
static fdctrl_t *floppy_controller;
static RTCState *rtc_state;
static PITState *pit;
@@ -443,7 +440,8 @@
fw_cfg = fw_cfg_init(BIOS_CFG_IOPORT, BIOS_CFG_IOPORT + 1, 0, 0);
fw_cfg_add_i32(fw_cfg, FW_CFG_ID, 1);
fw_cfg_add_i64(fw_cfg, FW_CFG_RAM_SIZE, (uint64_t)ram_size);
- fw_cfg_add_bytes(fw_cfg, FW_CFG_ACPI_TABLES, acpi_tables, acpi_tables_len);
+ fw_cfg_add_bytes(fw_cfg, FW_CFG_ACPI_TABLES, (uint8_t *)acpi_tables,
+ acpi_tables_len);
}
/* Generate an initial boot sector which sets state and jump to
Modified: trunk/hw/pc.h
===================================================================
--- trunk/hw/pc.h 2009-03-07 15:46:23 UTC (rev 6737)
+++ trunk/hw/pc.h 2009-03-07 15:50:18 UTC (rev 6738)
@@ -101,6 +101,9 @@
/* acpi.c */
extern int acpi_enabled;
+extern char *acpi_tables;
+extern size_t acpi_tables_len;
+
i2c_bus *piix4_pm_init(PCIBus *bus, int devfn, uint32_t smb_io_base,
qemu_irq sci_irq);
void piix4_smbus_register_device(SMBusDevice *dev, uint8_t addr);
reply other threads:[~2009-03-07 15:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1Lfyn4-0007qJ-Uk@cvs.savannah.gnu.org \
--to=blauwirbel@gmail.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).