...@apple.com; devel@edk2.groups.io
Cc: Chaganty, Rangasai V ; Dong, Eric
; Gao, Liming ; Ni, Ray
Subject: RE: [edk2-devel] [edk2-platforms][PATCH V1 0/3] Add FW Boot Media
Device Indicator
Thanks for sharing. You articulated well why I also don't think this is
required in MdePkg. My
description o
ps.io; Kubacki, Michael A
Cc: Chaganty, Rangasai V ; Dong, Eric
; Gao, Liming ; Ni, Ray
Subject: Re: [edk2-devel] [edk2-platforms][PATCH V1 0/3] Add FW Boot Media
Device Indicator
Since I was around back in the Intel Tiano days and I've worked on all the PI
specs I can share the history.
Since I was around back in the Intel Tiano days and I've worked on all the PI
specs I can share the history.
The reset vector is a hardware thing. It is usually at the top or bottom of the
address space. For x86 it is at the TOP of the ROM and that is why the FV has a
VoluteTop file GUID that
In platforms built for boot media other than SPI flash there has been a
compelling
need for silicon and platform code to be aware of the firmware boot media but
apart from the UEFI variable driver (which is a special case being addressed
here - https://github.com/makubacki/edk2/tree/storage_agnost
I am not sure if there is a silicon scope around the FirmwareBootMediaLib. Have
we considered adding this interface to MdePkg, instead?
-Original Message-
From: Kubacki, Michael A
Sent: Monday, September 30, 2019 6:16 PM
To: devel@edk2.groups.io
Cc: Chaganty, Rangasai V ; Dong, Eric
; G
This patch series introduces a mechanism for determining the firmware
boot media device. This allows the firmware boot media to be discovered
through a standardized API.
Traditionally, most systems have only supported firmware storage on SPI
flash. Presently, several other storage technologies are
