From: Patrick Ohly <patrick.ohly@intel.com>
To: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V3 0/3] Add UEFI firmware for qemux86*
Date: Fri, 28 Aug 2015 10:33:53 +0200 [thread overview]
Message-ID: <1440750833.3006.85.camel@intel.com> (raw)
In-Reply-To: <55DF69EF.9050303@linux.intel.com>
On Thu, 2015-08-27 at 14:50 -0500, Leonardo Sandoval wrote:
> On 08/27/2015 08:19 AM, Patrick Ohly wrote:
> > When I use runqemu, it ends up invoking qemu with "-vga vmware". With
> > that, I don't see any output from TianoCore and booting hangs. It boots
> > when disabling graphical output ("serial nographic" as parameter of
> > runqemu) or when explicitly selecting a different graphics
> > ("'qemuparams=-vga std'"). Might be worthwhile adding to the commit
> > message.
>
> In the 3/3 commit's description, there is a command line with the
> nographic parameter. I did not test with any other kernel command line.
True, that example works. But it is not clear that the "nographic" is
important. Being explicit about it and adding the graphical case would
be useful.
> > Do you happen to know how non-volatile EFI variables are handled? There
> > are several posts from around 2012 saying that qemu does not support
> > storing nvram persistently (for example, [1]). I've not seen anything
> > more recent directly contradicting that, but there seems to be
> > something, at least in Fedora [2]. That patch mentions that "OVMF [...]
> > works in two
> > modes: 1) Code and UEFI variable store is mixed in one file. ...".
> >
>
> sorry, I do not know.
I think this will require further work - see my comment on the runqemu
patch.
Do you have time for a forth revision?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
prev parent reply other threads:[~2015-08-28 8:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 20:07 [PATCH V3 0/3] Add UEFI firmware for qemux86* leonardo.sandoval.gonzalez
2015-07-14 20:07 ` [PATCH V3 1/3] iasl: Recipe taken from the luv-yocto repository leonardo.sandoval.gonzalez
2015-09-12 22:00 ` Richard Purdie
2015-09-13 7:13 ` Fathi Boudra
2015-09-14 15:37 ` Leonardo Sandoval
2015-07-14 20:07 ` [PATCH V3 2/3] ovmf: Recipe taken from " leonardo.sandoval.gonzalez
2015-07-14 20:07 ` [PATCH V3 3/3] runqemu: Define OECORE_MACHINE_SYSROOT on setup_sysroot leonardo.sandoval.gonzalez
2015-08-28 7:29 ` Patrick Ohly
2015-08-28 13:34 ` Leonardo Sandoval
2015-08-28 18:08 ` Patrick Ohly
2015-09-02 19:40 ` Leonardo Sandoval
2015-09-04 19:13 ` Patrick Ohly
2015-08-27 13:19 ` [PATCH V3 0/3] Add UEFI firmware for qemux86* Patrick Ohly
2015-08-27 14:28 ` Paul Eggleton
2015-08-27 19:50 ` Leonardo Sandoval
2015-08-28 8:33 ` Patrick Ohly [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=1440750833.3006.85.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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