On Mon, 2017-01-09 at 19:50 -0800, Ricardo Neri wrote:
> On Wed, 2017-01-04 at 10:43 +0100, Patrick Ohly wrote:
> > To
> > test that supporting separate code and variables also works, I've
> > implemented that locally so that ovmf.fd ovmf_secboot.fd, ovmf_code.fd,
> > ovmf_secboot_code.fd and ovmf_
On Wed, 2017-01-04 at 10:43 +0100, Patrick Ohly wrote:
> On Wed, 2016-12-28 at 15:33 -0800, Ricardo Neri wrote:
> > On Wed, 2016-12-21 at 14:11 +0100, Patrick Ohly wrote:
> > > +# File name of a OVMF BIOS file, to be added with -drive
> > > if=pflash.
> > > +# Found in the same plac
On Wed, 2016-12-28 at 15:33 -0800, Ricardo Neri wrote:
> On Wed, 2016-12-21 at 14:11 +0100, Patrick Ohly wrote:
> > +# File name of a OVMF BIOS file, to be added with -drive
> > if=pflash.
> > +# Found in the same places as the rootfs, with or without one
> > of
> > +# these
On Wed, 2016-12-21 at 14:11 +0100, Patrick Ohly wrote:
> +# File name of a OVMF BIOS file, to be added with -drive
> if=pflash.
> +# Found in the same places as the rootfs, with or without one
> of
> +# these suffices: qcow2, bin.
> +# Setting one also adds "-vga std
In the simplest case, "runqemu qemux86 qcow2 ovmf" for an
EFI-enabled image in the qcow2 format will locate the OVMF firmware file,
override the graphics hardware with "-vga std" because that is all
that OVMF supports, and boot with UEFI enabled. This depends on
"bitbake ovmf" deploying a "ovmf.qc
