From: Jordan Justen <jljusten@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Gleb Natapov <gleb@redhat.com>,
Kevin O'Connor <kevin@koconnor.net>,
qemu-devel <qemu-devel@nongnu.org>,
Michal Suchanek <hramrach@centrum.cz>,
Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] OVMF Google Summer of Code ideas
Date: Tue, 8 Mar 2011 09:00:05 -0800 [thread overview]
Message-ID: <AANLkTikTTe0_f9BKSFroUxKv78UdS332BiQw3E2PUct9@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinMGXaAi95PC9V+2x9N6j6JMmxH17OKTEoc88zi@mail.gmail.com>
On Mon, Mar 7, 2011 at 23:18, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Tue, Mar 8, 2011 at 12:54 AM, Jordan Justen <jljusten@gmail.com> wrote:
>> The biggest issue that you guys care about for OVMF is a lack of
>> legacy bios compatibility (CSM). There has been no progress in this
>> area. (However, it has now been suggested by someone on our dev list
>> for a potential Google Summer of Code project. We will have to see if
>> anything comes of this...)
>
> That would be cool. Is there a way to just embed SeaBIOS? Or do the
> UEFI APIs still need to be around when CSM kicks in?
Yes, the UEFI system is still in place. The UEFI part still handles
the majority of platform init, and calls into the CSM at various
points. The CSM returns back to UEFI for all CSM calls, except the
legacy boot.
-Jordan
next prev parent reply other threads:[~2011-03-08 17:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 4:12 [Qemu-devel] OVMF Google Summer of Code ideas Jordan Justen
2011-03-06 15:29 ` Michal Suchanek
2011-03-06 21:15 ` Jordan Justen
2011-03-07 9:48 ` Stefan Hajnoczi
2011-03-08 0:54 ` Jordan Justen
2011-03-08 7:18 ` Stefan Hajnoczi
2011-03-08 8:26 ` Gleb Natapov
2011-03-08 17:13 ` Jordan Justen
2011-03-09 10:16 ` Gleb Natapov
2011-03-09 18:34 ` Jordan Justen
2011-03-08 17:00 ` Jordan Justen [this message]
2011-03-09 2:23 ` Kevin O'Connor
2011-03-09 5:34 ` Jordan Justen
2011-03-09 13:43 ` Natalia Portillo
2011-03-09 18:44 ` Jordan Justen
2011-03-09 23:20 ` Natalia Portillo
2011-03-07 10:22 ` Peter Maydell
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=AANLkTikTTe0_f9BKSFroUxKv78UdS332BiQw3E2PUct9@mail.gmail.com \
--to=jljusten@gmail.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=hramrach@centrum.cz \
--cc=kevin@koconnor.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 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).