qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jordan Justen <jljusten@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] pc.c: Add UEFI IA32 & X64 machine types.
Date: Mon, 10 Aug 2009 13:52:54 -0500	[thread overview]
Message-ID: <4A806C86.6030504@codemonkey.ws> (raw)
In-Reply-To: <1249782222-6724-1-git-send-email-jljusten@gmail.com>

Jordan Justen wrote:
> For i386, this change adds a 'uefi' machine type.  For x86_64, this
> change adds 'uefi' and 'uefi32' machine types.
>   

Why are uefi32 machines explicitly needed?

How does one build the uefi roms?

Is uefi all that useful in the absence of a CSM?  Wouldn't it make more 
sense to add a CSM to uefi and then switch the default pc to use uefi?

> These machine types will load different bios and video bios images:
>   

Regards,

Anthony Liguori

  reply	other threads:[~2009-08-10 18:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-09  1:43 [Qemu-devel] [PATCH] pc.c: Add UEFI IA32 & X64 machine types Jordan Justen
2009-08-10 18:52 ` Anthony Liguori [this message]
2009-08-10 19:33   ` Jordan Justen

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=4A806C86.6030504@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=jljusten@gmail.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).