From: Leif Lindholm <leif.lindholm@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Andre <andreesteve@gmail.com>,
edk2-devel@lists.01.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: Can OVMF run on an emulated QEMU ARM vexpress-a9?
Date: Mon, 12 Jun 2017 17:43:36 +0100 [thread overview]
Message-ID: <20170612164336.GM26676@bivouac.eciton.net> (raw)
In-Reply-To: <c40331d9-6700-b22a-00aa-ceeccd5fcfbd@redhat.com>
On Mon, Jun 12, 2017 at 06:28:45PM +0200, Laszlo Ersek wrote:
> There used to be ArmPlatformPkg/ArmVExpressPkg (now defunct I think?),
Not quite defunct, just partially migrated to (and used by) the below.
> and there's
> <https://git.linaro.org/uefi/OpenPlatformPkg.git/tree/Platforms/ARM/VExpress>
> as well.
>
> I think the latter might just give you what you want.
There would probably be some effort required, creating .dsc/.fdf files
- but the vast majority of code should be available. The only 32-bit
platform still supported is "TC2", described by ArmVExpress-CTA15-A7.dsc.
Depending on exactly how much the qemu vexpress-a9 platform models,
and how, some development and/or code archeology may be required.
vexpress-a15 could actually be a lot less effort, since the cortex-a15
contains only architectural caches, whereas the cortex-a9 hardware
platforms used an external L2 (PL310).
If someone would be keen enough to provide an ARM Trusted Firmware
port for CortexA9x4, I would be happy to resurrect that platform port.
But I wouldn't want to bring back the "start from EL3" version.
> You might get away running builds of existent firmware platforms (DSC
> files) in non-matching environments, but the platform integration will
> suffer. This ranges from "crashes without a single log message" to "some
> optional UEFI protocols are missing".
Indeed.
/
Leif
prev parent reply other threads:[~2017-06-12 16:42 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
2017-06-12 19:50 ` Ard Biesheuvel
2017-06-12 16:43 ` Leif Lindholm [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-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=20170612164336.GM26676@bivouac.eciton.net \
--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