u-boot.git/lib/vsprintf.c, branch v2020.04-rc4

lib: Always build support for formatting MAC and IP address

2019-12-09T15:47:41+00:00

Even if not communicating over the network in U-Boot, code may be manipulating
and storing IP or MAC addresses to pass to Linux, etc.

Signed-off-by: Joe Hershberger

Move strtomhz() to vsprintf.h

2019-12-02T23:23:09+00:00

At present this function sits in its own file but it does not really
justify it. There are similar string functions in vsprintf.h, so move it
there. Also add the missing function comment.

Use the vsprintf.h include file explicitly where needed.

Signed-off-by: Simon Glass 
Reviewed-by: Tom Rini

lib/vsprintf: allow printing upper case GUIDs

2019-06-07T14:52:30+00:00

In the UEFI context GUIDs are expected to be rendered in upper case.

The patch uses the formerly unused bit 1 of the parameter str_format
of function uuid_bin_to_str() to indicate if we need upper or lower case
output.

Function uuid_string() in vsprint.c is adjusted to correctly set the bit
depending on the print format code.

%pUb: 01020304-0506-0708-090a-0b0c0d0e0f10
%pUB: 01020304-0506-0708-090A-0B0C0D0E0F10
%pUl: 04030201-0605-0807-090a-0b0c0d0e0f10
%pUL: 04030201-0605-0807-090A-0B0C0D0E0F10

Up to this point only a diagnostic message in mount_ubifs() using '%pUB' is
concerned by the change. Further patches are needed to adjust the UEFI
subsystem.

A unit test is provided inside the ut_print command.

Signed-off-by: Heinrich Schuchardt

efi_loader: make device path to text protocol customizable

2019-05-12T18:54:22+00:00

The device path to text protocol is not needed for EBBR compliance. So
let's make it a customizable option.

Signed-off-by: Heinrich Schuchardt

lib/vsprintf: remove #include from vsprintf.c

2019-05-03T11:23:17+00:00

common.h already includes uuid.h

Signed-off-by: Heinrich Schuchardt

vsprintf: Support phys_addr_t specifier unconditionally

2019-04-12T02:10:05+00:00

When phys_addr_t printf specifier support was first introduced in commit
1eebd14b7902 ("vsprintf: Add modifier for phys_addr_t"), it was enabled
only if CONFIG_CMD_NET was selected. Since physical addresses are not
unique to networking support it doesn't make sense to conditionally add
it in those cases only. Move support for it outside of the CMD_NET guard
so that the specifier is always supported.

Signed-off-by: Thierry Reding 
Reviewed-by: Simon Glass

lib/vsprintf: print '?' for illegal Unicode sequence

2019-02-16T14:42:20+00:00

Commit 0e66c10a7d80 ("lib: vsprintf: avoid overflow printing UTF16
strings") broke the Unicode unit tests: an illegal UTF16 code point
should be printed as '?'.

Fixes: 0e66c10a7d80 ("lib: vsprintf: avoid overflow printing UTF16 strings")
Signed-off-by: Heinrich Schuchardt

lib: vsprintf: avoid overflow printing UTF16 strings

2019-02-13T08:40:06+00:00

We have to ensure while printing UTF16 strings that we do not exceed the
end of the print buffer.

Signed-off-by: Heinrich Schuchardt 
Reviewed-by: Simon Glass 
Signed-off-by: Alexander Graf

lib: vsprintf: correct printing of Unicode strings

2018-09-23T19:55:29+00:00

The width and precision of the printf() function refer to the number of
characters not to the number of bytes printed.

Signed-off-by: Heinrich Schuchardt 
Signed-off-by: Alexander Graf

efi_loader: rename utf16_strlen, utf16_strnlen

2018-09-23T19:55:29+00:00

The function names utf16_strlen() and utf16_strnlen() are misnomers.
The functions do not count utf-16 characters but non-zero words.
So let's rename them to u16_strlen and u16_strnlen().

In utf16_dup() avoid assignment in if clause.

Signed-off-by: Heinrich Schuchardt 
Signed-off-by: Alexander Graf