Since .utf8 UTF-8 unicode files might contain strings with unicode
code points larger than 16-bits, and UEFI only supports UTF-16
characters, we need to make sure that BaseTools rejects these strings.
Cc: Yingke D Liu
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jordan J
This verifies that a .uni file should contain UTF-16 data (with BOM)
or an error should be generated by AutoGen.UniClassObject when the
string file in processed.
Cc: Yingke D Liu
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jordan Justen
---
BaseTools/Tests/CheckUnicod
This verifies that UTF-16 (with BOM) is considered bad data in a .utf8
file.
It also verified that UTF-8 data in a .utf8 file does not generate an
error.
Cc: Yingke D Liu
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jordan Justen
---
BaseTools/Tests/CheckUnicodeSource
This command was used to convert the file:
iconv -f UTF-16 -t UTF-8 OvmfPkg/PlatformDxe/Platform.uni \
> OvmfPkg/PlatformDxe/Platform.utf8
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jordan Justen
---
OvmfPkg/PlatformDxe/Platform.inf | 2 +-
OvmfPkg/PlatformDx
With .uni UTF-16 files, it is impossible for unicode code points to be
larger than 0x.
To support .utf8 UTF-8 unicode files, we need to also deal with the
possibility that the UTF-8 file contains unicode code points larger
than 16-bits. Since UEFI only supports 16-bit string data, we make
UniC
This allows the unit tests to run without the errors logging to the
screen.
Cc: Yingke D Liu
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jordan Justen
---
BaseTools/Source/Python/Common/EdkLogger.py | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff -
This allows unit tests to easily include BaseTools python
modules. This is very useful for writing unit tests.
Actually, previously, we would do this when RunTests.py was executed,
so unit tests could easily import BaseTools modules, so long as they
were executed via RunTests.
This change allows
Since UEFI only support UTF-16LE strings internally, this simply
allows for another unicode the source file encoding.
The strings are still converted to UTF-16LE data for use in EDK II
source code.
Cc: Yingke D Liu
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jordan Jus
In .utf8 files, there is the possibility that 32-bit unicode code
points might be used in comments.
While a 32-bit unicode code points should be dissallowed in string
data, it should be allowed in comments.
Cc: Yingke D Liu
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: J
The UTF-16 .uni files are fairly annoying to work with:
* They must be checked in as 'binary' files
* It is difficult to produce a diff of changes
* UTF-8 is more likely to be supported by text editors
With some basic testing on Linux, it appears that UTF-8 works as
expected with UTF-8 files. Both
Since ArmVExpressSysConfigLib cannot be supported at runtime, restrict
its use to the types of modules that are currently using it legally.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel
---
ArmPlatformPkg/ArmVExpressPkg/Library/ArmVExpressSysConfigLib/Arm
Changes since v3:
- since v2's approach of returning RETURN_UNSUPPORTED when being invoked
after SetVirtualAddressMap() has been called turns out to be broken
for SEC modules, reinstate the module type restriction instead
- use a NULL implementation of ArmPlatformSysConfigLib for
DXE_RUNTIME_
The ArmVExpressSysConfigLib library does not (and cannot) runtime
remap its MMIO registers, so use a NULL implementation of the
ArmPlatformSysConfigLib library class for DXE_RUNTIME_DRIVER
type modules.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel
---
Arm
Since the default EfiResetSystemLib for VExpress cannot be used at
runtime (due to the fact that its MMIO registers need to be owned
by the OS and so cannot be runtime remapped), instead use PSCI calls
into EL3 at runtime.
Contributed-under: TianoCore Contribution Agreement 1.0
Reviewed-by: Olivie
Aaron,
Thanks for your comments. I check the code you provide, I found the input
maximum value(200) is bigger than the allowed maximum value(0x7F). So
vfrcompiler assume the maximum value is (INT (200) = -38) which is small than
minimum value(0), and the error raised.
Now I add code to do bound
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Eric Dong
---
.../Universal/DriverSampleDxe/NVDataStruc.h| 1 +
MdeModulePkg/Universal/DriverSampleDxe/Vfr.vfr | 13 ++
.../Universal/DriverSampleDxe/VfrStrings.uni | Bin 61414 -> 62662 bytes
.../Universa
Yes, the patches are specific for UEFI 2.5 EFI_NVME_PASS_THRU_PROTOCOL support.
If no further comments, I will check it in to EDKII open source repo(that is
the link you show below).
-Original Message-
From: Simon (Xiang) Lian-SSI [mailto:simon.l...@ssi.samsung.com]
Sent: Saturday, May
17 matches
Mail list logo