From: Avi Kivity <avi@redhat.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Glauber Costa <glommer@gmail.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Dustin Kirkland <kirkland@canonical.com>,
qemu-devel@nongnu.org, Alex Graf <alex@csgraf.de>
Subject: Re: [Qemu-devel] Re: [PATCH 1/4] Add GPL bios as a submodule
Date: Sun, 17 May 2009 21:03:45 +0300 [thread overview]
Message-ID: <4A105181.4070700@redhat.com> (raw)
In-Reply-To: <20090517175126.GA13426@shareable.org>
Jamie Lokier wrote:
> Avi Kivity wrote:
>
>> Let's only include seabios then and reject all patches to the bochs
>> bios. If that doesn't motivate people to switch, nothing will.
>>
>
> Is there a technical reason why should people switch, other than you
> want them to? Is Bochs BIOS broken in some difficult to fix way?
>
bochs bios is written in 16-bit assembly and a mix of 16-bit C and
32-bit gcc. It requires a special toolchain (bcc/dev86), the code is
(no disrespect to its authors) quite nasty.
seabios is mostly C (gcc, not dev86) and well written and maintained.
No doubt you could fix the bochs bios to have these attributes, but then
I'd ask if there is a technical reason why we should do that rather than
switch to seabios.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-05-17 18:03 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 15:28 [Qemu-devel] [PATCH 0/4][RFC] Bring ROM source into tree via git submodules Anthony Liguori
2009-05-17 15:28 ` [Qemu-devel] [PATCH 1/4] Add GPL bios as a submodule Anthony Liguori
2009-05-17 15:43 ` [Qemu-devel] " Avi Kivity
2009-05-17 15:49 ` Anthony Liguori
2009-05-17 16:23 ` Avi Kivity
2009-05-17 17:51 ` Jamie Lokier
2009-05-17 18:03 ` Avi Kivity [this message]
2009-05-17 18:05 ` Stanislav
2009-05-17 18:11 ` Avi Kivity
2009-05-17 18:37 ` Stanislav
2009-05-17 19:07 ` Avi Kivity
2009-05-17 22:12 ` Carl-Daniel Hailfinger
2009-05-17 22:40 ` Avi Kivity
2009-05-17 23:22 ` Anthony Liguori
2009-05-18 15:20 ` ron minnich
2009-05-18 2:40 ` Kevin O'Connor
2009-05-17 23:13 ` Anthony Liguori
2009-05-18 4:22 ` Jamie Lokier
2009-05-25 13:04 ` Carl-Daniel Hailfinger
2009-05-17 23:09 ` Anthony Liguori
2009-05-17 23:23 ` Avi Kivity
2009-05-17 23:31 ` Anthony Liguori
2009-05-17 23:40 ` Avi Kivity
2009-05-18 1:17 ` Anthony Liguori
2009-05-18 5:48 ` Avi Kivity
2009-05-17 17:10 ` Sebastian Herbszt
2009-05-17 15:28 ` [Qemu-devel] [PATCH 2/4] Add submodule for VGABios Anthony Liguori
2009-05-17 15:29 ` [Qemu-devel] [PATCH 3/4] Update makefile to build roms Anthony Liguori
2009-05-17 15:46 ` [Qemu-devel] " Avi Kivity
2009-05-17 15:47 ` Avi Kivity
2009-05-17 15:53 ` Anthony Liguori
2009-05-17 17:16 ` Avi Kivity
2009-05-17 23:10 ` Anthony Liguori
2009-05-17 22:04 ` Paul Brook
2009-05-17 23:28 ` Anthony Liguori
2009-05-17 23:43 ` Paul Brook
2009-05-18 1:18 ` Anthony Liguori
2009-05-18 4:24 ` Jamie Lokier
2009-05-18 8:25 ` Riku Voipio
2009-05-18 8:35 ` Avi Kivity
2009-05-17 15:29 ` [Qemu-devel] [PATCH 4/4] Allow tool chain to be specified for bios build Anthony Liguori
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=4A105181.4070700@redhat.com \
--to=avi@redhat.com \
--cc=alex@csgraf.de \
--cc=aliguori@us.ibm.com \
--cc=glommer@gmail.com \
--cc=jamie@shareable.org \
--cc=kirkland@canonical.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).