diff options
| author | Gabriel L. Somlo <somlo@cmu.edu> | 2015-03-19 14:20:44 -0400 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2015-03-25 13:37:10 +0100 |
| commit | 3a5c76baf312d83cb77c8faa72c5f7a477effed0 (patch) | |
| tree | ca47f6fc6823042867626009cee275626a93831d /hw/i386/pc.c | |
| parent | 8a5956ad6392f115521dad774055c737c49fb0dd (diff) | |
| download | qemu-3a5c76baf312d83cb77c8faa72c5f7a477effed0.zip qemu-3a5c76baf312d83cb77c8faa72c5f7a477effed0.tar.gz qemu-3a5c76baf312d83cb77c8faa72c5f7a477effed0.tar.bz2 | |
fw_cfg: factor out initialization of FW_CFG_ID (rev. number)
The fw_cfg documentation says this of the revision key (0x0001, FW_CFG_ID):
> A 32-bit little-endian unsigned int, this item is used as an interface
> revision number, and is currently set to 1 by all QEMU architectures
> which expose a fw_cfg device.
arm/virt doesn't. It could be argued that that's an error in
"hw/arm/virt.c"; on the other hand, all of the other fw_cfg providing
boards set the interface version to 1 manually, despite the device
coming from the same, shared implementation. Therefore, instead of
adding
fw_cfg_add_i32(fw_cfg, FW_CFG_ID, 1);
to arm/virt, consolidate all such existing calls in the fw_cfg
initialization code.
Signed-off-by: Gabriel Somlo <somlo@cmu.edu>
Message-Id: <1426789244-26318-1-git-send-email-somlo@cmu.edu>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'hw/i386/pc.c')
| -rw-r--r-- | hw/i386/pc.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/hw/i386/pc.c b/hw/i386/pc.c index a52d2af..a8e6be1 100644 --- a/hw/i386/pc.c +++ b/hw/i386/pc.c @@ -702,7 +702,6 @@ static FWCfgState *bochs_bios_init(void) * the APIC ID, not the "CPU index" */ fw_cfg_add_i16(fw_cfg, FW_CFG_MAX_CPUS, (uint16_t)apic_id_limit); - 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); |