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 14:02:10 +0000	[thread overview]
Message-ID: <CAKv+Gu8uH6=Q9prmwMref0BjBuU18qkqZcHNh+M-Cu+-pG-PQw@mail.gmail.com> (raw)
In-Reply-To: <20170601075533.000035be@bluestop.org>

On 1 June 2017 at 13:55, Rebecca Cran <rebecca@bluestop.org> wrote:
> On Thu, 1 Jun 2017 07:29:05 +0000
> Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>
>> 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?
>
> I'm using the OpenPlatformPkg tree from
> https://git.linaro.org/uefi/OpenPlatformPkg.git .
>
> The binary I was interested in is PreUefiFirmware.bin in
> https://git.linaro.org/uefi/OpenPlatformPkg.git/tree/Platforms/AMD/Styx/Overdrive1000Board/Binary .
>
> I should probably explain what problem I'm trying to solve. I'm working
> on NVDIMM support, and have been starting to plan work around
> making changes to the EDK2 to support the modules, starting with
> reading the DDR4 SPD data.
>
> However, the i2c access protocols etc. that I'd need appear to be
> implemented in the PreUefiFirmware.bin binary and are currently not
> exposed to UEFI drivers via the protocols from the PI spec.
>

The SoC has a separate System Control Processor (SCP), which is a
Cortex-A5 ARM core that has its own firmware. The source for this
firmware is not included in the FDK, nor is it (or any of the secure
firmware that /is/ included) based on PI/UEFI or EDK2. So if you need
I2C support in UEFI, you will need to add drivers for the Synopsys
Designware I2C controllers on this board. The FDK does not contain
anything useful, I'm afraid.


      reply	other threads:[~2017-06-01 14:01 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
2017-06-01 13:55   ` Rebecca Cran
2017-06-01 14:02     ` Ard Biesheuvel [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='CAKv+Gu8uH6=Q9prmwMref0BjBuU18qkqZcHNh+M-Cu+-pG-PQw@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