thanks Andrew.
If i use as you said
HD(1,GPT,E3AE6975-BACE-464E-
91E1-BB4FE9954047,0x800,0x31801)/\EFI\BOOT\BOOTAA64.EFI”
grub enter rescue mode.
it is happening since grub is getting loaded, however the prefix and root
are not set properly.
if i set manually, then normal command works.
log:
Th
Hi Varad,
Why do you want to you want to use SEC? Why x-loader do not directly jump to
PrePeiCore?
I was told you have a JTAG. Check you have a 'BL 0x.' at the base
address of your FV file 0x80048000.
This jump address should be the entrypoint of your PrePeiCore module.
Thanks,
Olivier
> -
The result of running:
find ArmP* -not -name "*.sh" -not -name "*.patch" -not -name "*.py" -exec
unix2dos {} \;
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Leif Lindholm
---
ArmPkg/Drivers/ArmGic/ArmGicLib.c |2 +-
ArmPkg/Drivers/CpuDxe/ArmV6/Exce
Thanks Leif,
As I told you before I need to extend the test in our CI (the test already
covers *.c/*.h/*.S/*.asm files) before fixing any new whitespace change to
prevent to fix it again.
And as we can see in this patch our current test are not good enough because
I can see some *.c files in your p
Dear Bruce,
In general the system firmware does not have protected time source so the
expiration date of the certificate is ignored for Secure Boot verification.
(A bad actor could just change the system date to re-enable a certificate.)
In a particular system design that did have a time source wi
Dear Bruce,
In general the system firmware does not have protected time source so the
expiration date of the certificate is ignored for Secure Boot verification.
(A bad actor could just change the system date to re-enable a certificate.)
In a particular system design that did have a time sourc
Volodymyr,
EDK-II build system is capable of also building drivers written to the EDK-I
standard.
This ability is called ECP. (http://tianocore.sourceforge.net/wiki/ECP )
The Macros you mention in your email would be used in an EDK-I driver.
EDK-II uses different methods including the .d
Hi,
The "#langdef" value used in various EDK-II *.uni files define
the language name in various ways, seemingly inconsistent.
Most use either:
#langdef en-US "english"
or:
#langdef en-US "English"
A few use:
#langdef en-US "en-US"
UefiShellInstall1CommandsLib.uni uses:
#la
Hi,
For the DP command, there are two different codebases, one in
ShellPkg and one in PerformancePkg, which differ significantly at the
source level. One is copyrighted one year later. One is English-only,
one also has a French translation (unlike any other EDK2 commands,
which are all English-onl
Hi,
ShellPkg's UefiShellDebug1CommandsLib.uni's STR_GET_HELP_BCFG string
has 2 truncated strings, see excerpt:
1: "To add a driver option #5\r\n"
2: " %EShell>%N bcfg driver add 5 mydriver.efi "My Driver
3: "To add a boot option #3\r\n"
4: " %EShell>%N bcfg boot add 3 osloader.efi "My OS
Lines
10 matches
Mail list logo
