From: Avi Kivity <avi@qumranet.com>
To: Paul Brook <paul@codesourcery.com>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: Re: [kvm-devel] [Qemu-devel] Fixing ACPI for Vista -- Source code for bios.bin vs. bochs CVS?
Date: Tue, 01 May 2007 09:42:21 +0300 [thread overview]
Message-ID: <4636E14D.4040003@qumranet.com> (raw)
In-Reply-To: <200704302011.45291.paul@codesourcery.com>
Paul Brook wrote:
> On Monday 30 April 2007, Nakajima, Jun wrote:
>
>> We found a way to get 32-bit Vista up on KVM by fixing bios.bin. And I
>> think it should be helpful to qemu as well. However, I'm not sure if the
>> binary file has been created simply by applying bios.diff to the latest
>> bochs CVS tree (actually I doubt it).
>>
>
> What makes you think this won't work? Have you tried it?
>
>
Regardless of whether it works or not, it would be nice to have a file
in qemu/pc-bios detailing the revision numbers of the sources taken from
bochs, synced on each update. Something like the output of
cvs status | awk '/^File:/ { file = $2 } /^ Working revision:/ {
printf("%-20s %s\n", file, $3) }'
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2007-05-01 6:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 19:04 [Qemu-devel] Fixing ACPI for Vista -- Source code for bios.bin vs. bochs CVS? Nakajima, Jun
2007-04-30 19:11 ` Paul Brook
2007-04-30 19:42 ` Anthony Liguori
2007-04-30 22:40 ` Nakajima, Jun
2007-05-01 6:42 ` Avi Kivity [this message]
2007-05-01 8:52 ` [Qemu-devel] Re: [kvm-devel] " Gilad Ben-Yossef
2007-05-01 22:09 ` [Qemu-devel] Re: Fixing ACPI for Vista -- Source code for bios.bin vs.bochs CVS? consul
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=4636E14D.4040003@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=paul@codesourcery.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).