Hi ,all
My name is Wengang, I am an employee of Hisilicon. Hisilicon and Linaro have a corporation in the Aspen Project. Now we have a problem in the design of Poplar board.
I want to know when run fastboot commands to flash the images to eMMC, which mode does the USB interface work on? (Host Mode or Device Mode or ..?)
Best Regards,
Wengang
This patchset adds support for creating a MM Standalone image suitable for
running on a Base FVP in the AArch64 execution state.
The core support for instantiating MM Standalone mode is being developed in the
following edk2-staging branch:
https://github.com/tianocore/edk2-staging/tree/AArch64StandaloneMm
This branch and the patchset should be combined to build a MM Standalone
image. The instructions for this will be updated in edk2-staging later.
The changes in this series are aimed at:
1. partitioning DRAM to set aside memory for the MM Standalone image
2. including the necessary modules to instantiate the Standalone MM on the Base
FVP
This patchset should be staged in a separate branch until it is clearer how the
MM Standalone image should be supported on common ARM platforms.
Achin Gupta (4):
Platforms/ARM/VExpress: Size DRAM to accommodate Standalone MM image
Platforms/ARM/VExpress: Define extents of MM communication buffer
Platforms/ARM/VExpress: Include MM communication protocol driver
Platforms/ARM/VExpress: Include UEFI Info application in FVP build
Platforms/ARM/VExpress/ArmVExpress-FVP-AArch64.dsc | 10 +++++++++-
Platforms/ARM/VExpress/ArmVExpress-FVP-AArch64.fdf | 4 ++++
2 files changed, 13 insertions(+), 1 deletion(-)
--
1.9.1
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi Leif,
Quick resend of the patchset with minor correction pointed in v3.
The code can be also found in github:
https://github.com/MarvellEmbeddedProcessors/edk2-open-platform/commits/opp…
We will pop the champagne after NonDiscoverable merge, but
thank you very much for your help and support getting all
Armada 70x0 stuff into the tree.
Best regards,
Marcin
Changelog:
v3 -> v4
* Change SPI_ID_SIZE to sizeof (UINT32)
* Add reviewed-by
v2 -> v3
* Rename header structure to MV_FIRMWARE_IMAGE_HEADER
* Add STATIC attribute where possible
* Improve flash probe (add comments, use UINT32, SPI_ID_SIZE define
and SwapBytes32)
* Use CalculateSum32() instead of custom implementation
* Improve prints when parsing image path
* Sort HiiGuid in Marvell.dec
* Improve help in .uni file
v1 -> v2
* Remove executing external shell commands from commandline - now
only local files can be burnt to flash
* Add MARVELL_SPI_FLASH_PROTOCOL and MARVELL_SPI_MASTER_PROTOCOL usage
* In order to be standalone command, enable detecting and configuring
SPI flash
* Style cleanup and new comments
Jan Dąbroś (2):
Applications/FirmwareUpdate: Add 'fupdate' comand to shell
Platforms/Marvell: Enable 'fupdate' command on Armada70x0 platform
Applications/FirmwareUpdate/FUpdate.c | 413 ++++++++++++++++++++++++++++++++
Applications/FirmwareUpdate/FUpdate.inf | 75 ++++++
Applications/FirmwareUpdate/FUpdate.uni | Bin 0 -> 5146 bytes
Platforms/Marvell/Armada/Armada.dsc.inc | 1 +
Platforms/Marvell/Marvell.dec | 1 +
5 files changed, 490 insertions(+)
create mode 100644 Applications/FirmwareUpdate/FUpdate.c
create mode 100644 Applications/FirmwareUpdate/FUpdate.inf
create mode 100644 Applications/FirmwareUpdate/FUpdate.uni
--
1.8.3.1