Bill,
The Python tools can tend to throw vs.flagging errors in the config files. Did
you happen to edit anything in *.inf,*.dsc, or *.fdf files? This could just be
a syntax error in those changes.
This error looks like trying to make the FV (Firmware Volume) and Ffs would be
one of the files
Thanks for taking all the feedbacks and update patches.
For the patch series: Reviewed-by: Chasel Chiu
> -Original Message-
> From: devel@edk2.groups.io On Behalf Of cbduggap
> Sent: Friday, April 5, 2024 10:06 AM
> To: devel@edk2.groups.io
> Subject: [edk2-devel] [PATCH v6 0/3]
Changes to update SecRamInitData UPD structure reserved
bytes as par the latest spec.
Cc: Sai Chaganty
Cc: Nate DeSimone
Cc: Chiu Chasel
Cc: Duggapu Chinni B
Signed-off-by: Duggapu Chinni B
---
.../SecFspWrapperPlatformSecLibSample/SecRamInitData.c | 7 +--
1 file changed, 5
Changes to update SecRamInitData as per New Spec
Cc: Sai Chaganty
Cc: Nate DeSimone
Cc: Chiu Chasel
Cc: Duggapu Chinni B
Signed-off-by: Duggapu Chinni B
---
.../SecFspWrapperPlatformSecLibSample/SecRamInitData.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
Changes to support spec changes
1. Remove usage of Pcd.
2. Change code to validate the Temporary Ram size input.
3. Consume the input saved in YMM Register
Cc: Sai Chaganty
Cc: Nate DeSimone
Cc: Chiu Chasel
Cc: Duggapu Chinni B
Signed-off-by: Duggapu Chinni B
---
This Patch will add changes to support FSP T new ARCH UPD
and Fix Bug in IntelFsp2WrapperPkg
cbduggap (3):
IntelFsp2Pkg: Fsp T new ARCH UPD Support
IntelFsp2WrapperPkg: Fsp T new ARCH UPD Support
IntelFsp2WrapperPkg: Fix UPD structure Reserved bytes
Hi Sir
I have problem when building android bootloader.
The log suggested I could mail you for help.
Can I have your suggestion to solve this error?
Thank you
The log:
build.py...
: error C0DE: Unknown fatal error when processing
From: Phillip Tennen
UsbMouseDxe was missing from the OVMF build description, so
the Simple Pointer Protocol wasn't usable from within QEMU.
Here's an example of somone getting tripped up by this:
https://forum.osdev.org/viewtopic.php?f=1=31572.
I worked around this by including the below
On 05.04.24 14:58, phil...@axleos.com wrote:
From: Phillip Tennen
UsbMouseDxe was missing from the OVMF build description, so
the Simple Pointer Protocol wasn't usable from within QEMU.
Here's an example of somone getting tripped up by this:
https://forum.osdev.org/viewtopic.php?f=1=31572.
I
On 05.04.24 14:58, phil...@axleos.com wrote:
From: Phillip Tennen
UsbMouseDxe was missing from the OVMF build description, so
the Simple Pointer Protocol wasn't usable from within QEMU.
Here's an example of somone getting tripped up by this:
https://forum.osdev.org/viewtopic.php?f=1=31572.
I
Merged as 6fb3cc05dc87..8707f835ae35
Thanks.
Regards,
Sami Mujawar
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#117456): https://edk2.groups.io/g/devel/message/117456
Mute This Topic: https://groups.io/mt/104351709/21656
Group
On Wed, Apr 3, 2024 at 10:27 AM levi.yun wrote:
>
> Hello all!
>
> while I see the code. I have one question related using Flexible Array
> Member.
>
> For example)
>
> ///
> /// Socket Type Data.
> ///
> typedef struct {
>EFI_ACPI_6_4_PMTT_COMMON_MEMORY_DEVICE CommonMemoryDeviceHeader;
>
On Fri, Apr 5, 2024 at 7:43 AM levi.yun wrote:
>
> Hi Michael! Thanks for answer.
>
> > Converting these to a flexible array member would not be
> a backwards compatible change.
>
> That's the point. But at least when I see the compiler used in tool_def.txt,
> there's no compiler which doesn't
Hi Michael! Thanks for answer.
> Converting these to a flexible array member would not be
a backwards compatible change.
That's the point. But at least when I see the compiler used in tool_def.txt,
there's no compiler which doesn't support to flexible array member.
Do we still need to consider
14 matches
Mail list logo
