From: Laszlo Ersek <lersek@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Andre <andreesteve@gmail.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Leif Lindholm (Linaro address)" <leif.lindholm@linaro.org>
Subject: Re: Can OVMF run on an emulated QEMU ARM vexpress-a9?
Date: Mon, 12 Jun 2017 21:38:01 +0200 [thread overview]
Message-ID: <2c75cb93-d4ee-15bd-637e-b883f7380731@redhat.com> (raw)
In-Reply-To: <CAKv+Gu8a6aW2A5wfhbQdQuMH5hPiTJwaxqh18AAmRGVSkhpLNA@mail.gmail.com>
(side track)
On 06/12/17 18:40, Ard Biesheuvel wrote:
> On 12 June 2017 at 18:28, Laszlo Ersek <lersek@redhat.com> wrote:
>> - ArmVirtPkg/ArmVirtQemuKernel.dsc:
>>
>> - Not really sure about the QEMU configuration for this, but see
>> commit 8de84d424221 ("ArmVirtPkg: implement ArmVirtQemuKernel",
>> 2016-02-05) for the intended use. I think Ard can explain it better.
>>
>
> The standard mach-virt machine you get when using -bios boots with the
> firmware image exposed as an emulated XIP NOR flash. Many ARM systems
> that boot with ARM trusted firmware don't run UEFI in place but load
> it into DRAM and execute it from there.
>
> So ArmVirtQemuKernel runs from DRAM instead. It borrows the Linux
> kernel boot protocol to achieve this, since it was already implemented
> by QEMU via -kernel (and -bios/-pflash omitted)
Ah! So you boot that firmware binary itself with the "-kernel" option;
is that right?
(I guess I'll finally understand why you called the DSC file
"ArmVirtQemuKernel" :) )
Thanks!
Laszlo
next prev parent reply other threads:[~2017-06-12 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 6:44 Can OVMF run on an emulated QEMU ARM vexpress-a9? Andre
2017-06-12 16:28 ` Laszlo Ersek
2017-06-12 16:40 ` Ard Biesheuvel
2017-06-12 19:38 ` Laszlo Ersek [this message]
2017-06-12 19:50 ` Ard Biesheuvel
2017-06-12 16:43 ` Leif Lindholm
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-list 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=2c75cb93-d4ee-15bd-637e-b883f7380731@redhat.com \
--to=devel@edk2.groups.io \
/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