From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Allow additions of ACPI tables from command line
Date: Thu, 12 Feb 2009 18:59:59 +0200 [thread overview]
Message-ID: <f43fc5580902120859h6dc2054cj6d09d55160a83583@mail.gmail.com> (raw)
In-Reply-To: <20090212163710.GD13234@redhat.com>
On 2/12/09, Gleb Natapov <gleb@redhat.com> wrote:
> On Thu, Feb 12, 2009 at 05:53:24PM +0200, Blue Swirl wrote:
> > On 2/12/09, Gleb Natapov <gleb@redhat.com> wrote:
> > > This is needed to dynamically add SLIC tables with Windows
> > > activation keys.
> >
> > > +--- a/bios/rombios32.c
> > > ++++ b/bios/rombios32.c
> > > +@@ -455,6 +455,8 @@ unsigned long bios_table_end_addr;
> > > + #define QEMU_CFG_SIGNATURE 0x00
> > > + #define QEMU_CFG_ID 0x01
> > > + #define QEMU_CFG_UUID 0x02
> > > ++#define FW_CFG_ARCH_LOCAL 0x8000
> > > ++#define FW_CFG_ACPI_TABLES (FW_CFG_ARCH_LOCAL + 0)
> >
> > Why don't you just copy the file hw/fw_cfg.h as is? It's designed to
> > be included even from assembler files.
> >
>
> Bochs is another project. We can copy the file once but than we will have to
> sync it each time it changes in qemu anyway.
But we have to sync anyway even if the defines are directly used in
Bochs files. With fw_cfg.h in Bochs, the sync would be 'cp', instead
of manual editing with copy/paste.
OpenBIOS uses verbatim copies of fw_cfg.h and firmware_abi.h.
next prev parent reply other threads:[~2009-02-12 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 8:10 [Qemu-devel] [PATCH] Allow additions of ACPI tables from command line Gleb Natapov
2009-02-12 15:53 ` Blue Swirl
2009-02-12 16:37 ` Gleb Natapov
2009-02-12 16:59 ` Blue Swirl [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-09 11:39 Gleb Natapov
2009-02-09 13:19 ` Anthony Liguori
2009-02-09 13:48 ` Gleb Natapov
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=f43fc5580902120859h6dc2054cj6d09d55160a83583@mail.gmail.com \
--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).