public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Rebecca Cran <rebecca@bluestop.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Reconfiguring the PEI blob for the Overdrive1000 (AMD A1100)
Date: Thu, 1 Jun 2017 07:29:05 +0000	[thread overview]
Message-ID: <CAKv+Gu8r41ZyBmRkx6445i_Zbtj1DT2YUdLX_ESA+SB2V+UmRw@mail.gmail.com> (raw)
In-Reply-To: <13080acc-202a-ee70-14ca-5152e94e9698@bluestop.org>

On 1 June 2017 at 02:31, Rebecca Cran <rebecca@bluestop.org> wrote:
> Hi,
>
> I recently got an ARM64 SoftIron Overdrive 1000 box which uses AMD's Opteron
> A1100, and while it's nice having most of the platform firmware be open
> source, the part I'm missing is the PEI, which is implemented in a binary
> blob. Apparently that is generated via a tool called the AMD Firmware
> Development Kit, but I can't find any reference to it outside of the edk2.
>
>
> Is there any way a user outside of AMD can get the Firmware Development Kit,
> or somehow else reconfigure the PEI binary? I'm asking because some work I'm
> starting out on has changes for the PEI, and while I could use Qemu it would
> be nice to also develop on real hardware.
>

Hi Rebecca,

Which PEI binary are you referring to? There is the PEI core, and a
collection of PEI modules (PEIMs) that do various platform related
things, including PCIe link training (and believe me, looking at that
code will make your eyes bleed), which is the only closed source PEIM
IIRC.

Whether you can get access to the FDK is a question I cannot answer,
but I don't think there are any people left at AMD working on the
Seattle project.

Which tree are you building from?


  reply	other threads:[~2017-06-01  7:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01  2:31 Reconfiguring the PEI blob for the Overdrive1000 (AMD A1100) Rebecca Cran
2017-06-01  7:29 ` Ard Biesheuvel [this message]
2017-06-01 13:55   ` Rebecca Cran
2017-06-01 14:02     ` Ard Biesheuvel

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=CAKv+Gu8r41ZyBmRkx6445i_Zbtj1DT2YUdLX_ESA+SB2V+UmRw@mail.gmail.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