From: Kevin O'Connor <kevin@koconnor.net>
To: Stanislav <stlintel@gmail.com>
Cc: 'Anthony Liguori' <aliguori@us.ibm.com>,
'Dustin Kirkland' <kirkland@canonical.com>,
'Glauber Costa' <glommer@gmail.com>,
qemu-devel@nongnu.org, 'Avi Kivity' <avi@redhat.com>,
'Alex Graf' <alex@csgraf.de>
Subject: Re: [Qemu-devel] Re: [PATCH 1/4] Add GPL bios as a submodule
Date: Sun, 17 May 2009 22:40:50 -0400 [thread overview]
Message-ID: <20090518024050.GA32602@morn.localdomain> (raw)
In-Reply-To: <000101c9d71e$8888fec0$999afc40$@com>
On Sun, May 17, 2009 at 09:37:26PM +0300, Stanislav wrote:
> > What does Coreboot give us over seabios?
> You asking :)
Coreboot and SeaBIOS don't compete - they complement each other.
Modern X86 systems have no memory access when they first power on -
the initial bootstrap code must scan the memory modules via the smbus
and then program the memory controller. Much of Coreboot is dedicated
to programming ram and other low-level details of the hardware.
SeaBIOS is a port of bochs bios to gcc. It provides support for
legacy 16bit interfaces, including loading an OS from
floppy/harddrive. Coreboot uses SeaBIOS to provide support for off
the shelf OSes (eg, Windows).
Much of what coreboot provides is unnecessary for an emulated machine.
> > Doesn't Coreboot use seabios for legacy OS?
>
> No idea ...
Yes - coreboot itself has no legacy interfaces - SeaBIOS provides that
support.
-Kevin
next prev parent reply other threads:[~2009-05-18 2:40 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
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 [this message]
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=20090518024050.GA32602@morn.localdomain \
--to=kevin@koconnor.net \
--cc=alex@csgraf.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=glommer@gmail.com \
--cc=kirkland@canonical.com \
--cc=qemu-devel@nongnu.org \
--cc=stlintel@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.