qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Guillem Jover <guillem@debian.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ROM sources and checkout dates or versions
Date: Fri, 24 Dec 2004 11:08:37 +0100	[thread overview]
Message-ID: <20041224100837.GA17389@zulo.hadrons.org> (raw)
In-Reply-To: <41CB4604.3030008@bellard.org>

Hi,

On Thu, Dec 23, 2004 at 11:26:12PM +0100, Fabrice Bellard wrote:
> It is a bad idea to use the BIOSes from Bochs because QEMU has specific 
> patches.

As I maintain the Debian Bochs packages as well, I have applied
those patches already, no problem here. :>

> Moreover, the recent Bochs BIOS may be incompatible with QEMU 
> (I need to look at them).

Well, yes that seems to be what we are experiencing. I'll try
latest Bochs CVS snapshots.

> You should include the QEMU BIOSes as-is in an 
> architecture independent Debian package.
> 
> I am relunctant to provide the source code because it would duplicate 
> the code from Bochs and it would need a build process I am not ready to 
> support.

Yes I can understand, and it would duplicate the code as well on
Debian, but we'll need those sources anyway if we have to provide a
standalone package for the BIOSes, we cannot ship binaries without
sources.

At least for Debian needs, just providing the sources in tarball
form and not supporting the build process would be just fine,
although suboptimal for all. But we can understand you may not
want that. =)

> The provided diffs are suffisant to build the BIOS because they 
> give the date and CVS version of the corresponding Bochs code.

Ok, if the patches are resyned on every release that would be enough.

thanks,
guillem

      reply	other threads:[~2004-12-24 11:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-23 13:40 [Qemu-devel] ROM sources and checkout dates or versions Guillem Jover
2004-12-23 22:26 ` Fabrice Bellard
2004-12-24 10:08   ` Guillem Jover [this message]

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=20041224100837.GA17389@zulo.hadrons.org \
    --to=guillem@debian.org \
    --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).