qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Volker Ruppert <info@vruppert.de>
Cc: kvm developers <kvm@vger.kernel.org>,
	Gleb Natapov <gleb@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
	bochs developers <bochs-developers@lists.sourceforge.net>,
	Paul Brook <paul@codesourcery.com>,
	Sebastian Herbszt <herbszt@gmx.de>
Subject: Re: [Qemu-devel] [PATCH 0/3] Add BIOS splash image support
Date: Thu, 18 Dec 2008 13:46:47 -0800	[thread overview]
Message-ID: <494AC4C7.4000005@zytor.com> (raw)
In-Reply-To: <200812180959.25572.info@vruppert.de>

Volker Ruppert wrote:
> Hi all!
> 
>>> This would be the best solution.  How do the bochs folks feel about this?
>> There is the pcbios project available at
>> http://savannah.nongnu.org/projects/pcbios It seems fairly out of date tho.
>> Volker, you happen to know the status?
> 
> The PCBIOS project was based on the Bochs BIOS and started by Alex Beregszaszi 
> in summer 2005. He was the project admin and I was a normal project member. 
> We wanted to continue the Bochs BIOS development as a separate project. A few 
> weeks later I no longer had CVS write access. I had a look at the project 
> page on Savannah and found 0 members! I don't know what happend there. Alex 
> had no time to take care of it and some time later he disappeared. So I 
> continued the Bochs BIOS development inside of the Bochs project as usual.
> 

So I guess it comes down to: should we re-try to set up a separate BIOS
project?

This is a fairly big deal... there are by now a number of consumers of
this BIOS beyond Bochs: at least Qemu, KVM, and Coreboot all use it.  As
such, it would be highly advantageous if the core project was separate
and maintained in a DSCM (e.g. git or hg) so that a consumer who needs
to maintain their own tweaks can do so in a sane manner.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

  reply	other threads:[~2008-12-18 21:52 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 [this message]
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
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=494AC4C7.4000005@zytor.com \
    --to=hpa@zytor.com \
    --cc=blauwirbel@gmail.com \
    --cc=bochs-developers@lists.sourceforge.net \
    --cc=gleb@redhat.com \
    --cc=herbszt@gmx.de \
    --cc=info@vruppert.de \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --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).