From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rebecca@bluestop.org>
Received: from muon.cran.org.uk (muon.bluestop.org
 [IPv6:2605:7700:0:8:1:0:4a32:3323])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ml01.01.org (Postfix) with ESMTPS id 25B3521C93EC7
 for <edk2-devel@lists.01.org>; Thu,  1 Jun 2017 06:54:33 -0700 (PDT)
Received: from muon.bluestop.org (localhost [127.0.0.1])
 by muon.cran.org.uk (Postfix) with ESMTP id DB5D275AF0;
 Thu,  1 Jun 2017 13:55:33 +0000 (UTC)
Received: from muon.cran.org.uk ([127.0.0.1])
 by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id jvCIbMRVofrb; Thu,  1 Jun 2017 13:55:32 +0000 (UTC)
Received: from localhost (unknown [IPv6:2601:681:4300:fd:58ad:3f7c:ac95:1e42])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
 bits)) (No client certificate requested)
 by muon.cran.org.uk (Postfix) with ESMTPSA;
 Thu,  1 Jun 2017 13:55:32 +0000 (UTC)
Date: Thu, 1 Jun 2017 07:55:33 -0600
From: Rebecca Cran <rebecca@bluestop.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Message-ID: <20170601075533.000035be@bluestop.org>
In-Reply-To: <CAKv+Gu8r41ZyBmRkx6445i_Zbtj1DT2YUdLX_ESA+SB2V+UmRw@mail.gmail.com>
References: <13080acc-202a-ee70-14ca-5152e94e9698@bluestop.org>
 <CAKv+Gu8r41ZyBmRkx6445i_Zbtj1DT2YUdLX_ESA+SB2V+UmRw@mail.gmail.com>
X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; i686-w64-mingw32)
MIME-Version: 1.0
Subject: Re: Reconfiguring the PEI blob for the Overdrive1000 (AMD A1100)
X-BeenThere: edk2-devel@lists.01.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: EDK II Development  <edk2-devel.lists.01.org>
List-Unsubscribe: <https://lists.01.org/mailman/options/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=unsubscribe>
List-Archive: <http://lists.01.org/pipermail/edk2-devel/>
List-Post: <mailto:edk2-devel@lists.01.org>
List-Help: <mailto:edk2-devel-request@lists.01.org?subject=help>
List-Subscribe: <https://lists.01.org/mailman/listinfo/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jun 2017 13:54:33 -0000
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

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.

-- 
Rebecca