Skip to content
This repository was archived by the owner on Oct 28, 2019. It is now read-only.

Conversation

@hzhuang1
Copy link

Load fastboot from FV instead. Then we could avoid to load fastboot from ESP.

BdsFileSystemSupport() checks Handle first before validating device
path of file. There's the potential issue at here.

BdsConnectAndUpdateDevicePath() will skip to locate handle if it's
file or memory mapped. Then BdsFileSystemSupport() tries to use
the invalid Handle when it's not file path in file system.

Now check the device path first. If it's not file path in file system,
return directly.

Signed-off-by: Haojian Zhuang <haojian.zhuang@linaro.org>
BdsConnectAndUpdateDevicePath() won't set right handle if device path
is file path or memory mapped. Now try to tranverse all handles for
FvFile in Fv.

Signed-off-by: Haojian Zhuang <haojian.zhuang@linaro.org>
Add AndroidFastbootApp.dsc file. Then it's possible to build
AndroidFastbootApp.efi as module.

It could be embedded in firmware volume by this way.

Signed-off-by: Haojian Zhuang <haojian.zhuang@linaro.org>
Prebuild AndroidFastbootApp with AArch64 and Arm version.

Signed-off-by: Haojian Zhuang <haojian.zhuang@linaro.org>
Signed-off-by: Haojian Zhuang <haojian.zhuang@linaro.org>
Use FvFile to reference AndroidFastbootApp.efi. It's used when
AndroidFastbootApp.efi doesn't exist in ESP.

Signed-off-by: Haojian Zhuang <haojian.zhuang@linaro.org>
hzhuang1 added a commit to hzhuang1/edk2 that referenced this pull request Apr 16, 2018
Revert "EmbeddedPkg/AndroidFastboot: add delay before reboot"
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant