From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 0/3] Add BIOS splash image support
Date: Wed, 17 Dec 2008 12:01:38 -0600 [thread overview]
Message-ID: <49493E82.8060500@codemonkey.ws> (raw)
In-Reply-To: <20081217171724.GC7215@redhat.com>
Gleb Natapov wrote:
>> BTW, a few interruptions later I meanwhile had the chance to realize
>> that QEMU's bios.diff does not yet carry and fw_cfg bits, right? Does
>> its binary include them? Or is this currently kvm-only stuff?
>>
>> <confused> Jan
>>
>>
> AFAIK Anthony merges latest version of the BIOS in qemu now. I hope it
> will commit it soon.
>
I'm mirroring the Bochs CVS tree into git right now which I will then
post to a repo on repo.or.cz. This way, we can keep track of the
changeset in that repo. Otherwise, we have no way of keeping track of
which revision we're based on without using a formal release.
Regards,
Anthony Liguori
> --
> Gleb.
>
>
>
next prev parent reply other threads:[~2008-12-17 18:02 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 15:20 [Qemu-devel] [PATCH 0/3] Add BIOS splash image support Laurent Vivier
2008-12-16 15:20 ` [Qemu-devel] [PATCH 1/3] Correct fw_cfg_add_callback() Laurent Vivier
2008-12-16 15:20 ` [Qemu-devel] [PATCH 2/3] [BIOS] Add splash image support Laurent Vivier
2008-12-16 15:20 ` [Qemu-devel] [PATCH 3/3] [QEMU] Add BIOS splash image Laurent Vivier
2008-12-16 15:33 ` Andreas Färber
2008-12-16 17:22 ` Laurent Vivier
2008-12-16 16:16 ` Blue Swirl
2008-12-16 17:32 ` Laurent Vivier
2008-12-16 17:41 ` Blue Swirl
2008-12-16 17:58 ` Laurent Vivier
2008-12-16 20:06 ` [Qemu-devel] [PATCH 0/3] Add BIOS splash image support Blue Swirl
2008-12-16 20:28 ` Anthony Liguori
2008-12-16 20:46 ` Blue Swirl
2008-12-16 21:51 ` Laurent Vivier
2008-12-17 0:10 ` Carl-Daniel Hailfinger
2008-12-17 13:09 ` Laurent Vivier
2008-12-17 16:21 ` [Bochs-developers] " Carl-Daniel Hailfinger
2008-12-17 22:58 ` [Bochs-developers] [Qemu-devel] [PATCH 0/3] Add BIOS splashimage support Sebastian Herbszt
2008-12-17 11:03 ` [Qemu-devel] [PATCH 0/3] Add BIOS splash image support Daniel P. Berrange
2008-12-17 13:18 ` Paul Brook
2008-12-17 13:45 ` Jan Kiszka
2008-12-17 13:55 ` Gleb Natapov
2008-12-17 14:53 ` Jan Kiszka
2008-12-17 15:06 ` Jan Kiszka
2008-12-17 15:17 ` Paul Brook
2008-12-17 16:35 ` Jan Kiszka
2008-12-17 17:14 ` Anthony Liguori
2008-12-17 18:30 ` Jan Kiszka
2008-12-17 18:43 ` Anthony Liguori
2008-12-17 18:09 ` Andreas Färber
2008-12-17 17:15 ` Anthony Liguori
2008-12-17 22:28 ` Sebastian Herbszt
2008-12-18 8:59 ` Volker Ruppert
2008-12-18 21:46 ` H. Peter Anvin
2008-12-17 17:12 ` Carl-Daniel Hailfinger
2008-12-17 14:49 ` Gerd Hoffmann
2008-12-17 14:54 ` Jan Kiszka
2008-12-17 15:04 ` Kevin Wolf
2008-12-17 15:26 ` Daniel P. Berrange
2008-12-17 16:44 ` [Qemu-devel] " Jan Kiszka
2008-12-17 17:06 ` Gildas
2008-12-17 17:22 ` M. Warner Losh
2008-12-17 17:17 ` Gleb Natapov
2008-12-17 18:01 ` Anthony Liguori [this message]
2008-12-17 22:03 ` [Qemu-devel] " Sebastian Herbszt
2008-12-17 22:09 ` [Qemu-devel] " Anthony Liguori
2008-12-17 14:01 ` [Qemu-devel] " Daniel P. Berrange
2008-12-17 13:51 ` Kevin O'Connor
2008-12-17 21:58 ` [Qemu-devel] Re: [Bochs-developers] " Sebastian Herbszt
2008-12-17 23:24 ` Laurent Vivier
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=49493E82.8060500@codemonkey.ws \
--to=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).