- Sep 23, 2018
-
-
Heinrich Schuchardt authored
This patch provides a define to initialize a table that maps lower to capital letters for Unicode code point 0x0000 - 0xffff. Signed-off-by:
Heinrich Schuchardt <xypron.glpk@gmx.de> Signed-off-by:
Alexander Graf <agraf@suse.de>
-
Alexander Graf authored
We register the console in/out protocol on the loaded image handle, but never tell anyone about it in the systab. Because of this Shell.efi can not find the input protocol. So let's add a proper reference. Signed-off-by:
-
Heinrich Schuchardt authored
We have moved generating html documentation with Sphinx. %s/Return Value/Return/g Signed-off-by:
-
Heinrich Schuchardt authored
Correct the description of efi_update_capsule(). Signed-off-by:
-
Heinrich Schuchardt authored
Fix multiple typos Signed-off-by:
-
Heinrich Schuchardt authored
Fix numerous typos. Signed-off-by:
-
Stephen Warren authored
This reverts commit ccfc78b8. Now that the underlying issue is fixed, we can revert the revert and hence restore the original EFI code. Signed-off-by:
Stephen Warren <swarren@nvidia.com> Signed-off-by:
-
Stephen Warren authored
Tegra U-Boot ensures that board_get_usable_ram_top() never returns a value over 4GB, since some peripherals can't access such addresses. However, on systems with more than 2GB of RAM, RAM bank 1 does describe this extra RAM, so that Linux (or whatever OS) can use it, subject to DMA limitations. Since board_get_usable_ram_top() points at the top of RAM bank 0, the memory locations describes by RAM bank 1 are not mapped by U-Boot's MMU configuration, and so cannot be used for anything. For some completely inexplicable reason, U-Boot's EFI support ignores the value returned by board_get_usable_ram_top(), and EFI memory allocation routines will return values above U-Boot's RAM top. This causes U-Boot to crash when it accesses that RAM, since it isn't mapped by the MMU. One use-case where this happens is TFTP download of a file on Jetson TX1 (p2371-2180). This change explicitly tells the EFI code that this extra RAM should not be used, thus avoiding the crash. A previous attempt to make EFI honor board_get_usable_ram_top() was rejected. So, this patch will need to be replicated for any board that implements board_get_usable_ram_top(). Fixes: aa909462 ("efi_loader: efi_allocate_pages is too restrictive") Signed-off-by:
-
Stephen Warren authored
Use CONFIG_IS_ENABLED(EFI_LOADER) to avoid explicitly checking CONFIG_SPL too. This simplifies the conditional. Signed-off-by:
-
Heinrich Schuchardt authored
Remove functions: - utf8_to_utf16() - utf16_strcpy() - utf16_strdup() Signed-off-by:
-
Heinrich Schuchardt authored
The number of bytes in an utf-8 string is an upper limit for the number of words in the equivalent utf-16 string. In so far the inumbant coding works correctly. For non-ASCII characters the utf-16 string is shorter. With the patch only the necessary buffer size is allocated for the load options. Signed-off-by:
-
Heinrich Schuchardt authored
The length of a string printed to the console by the EFI_SIMPLE_TEXT_OUTPUT_PROTOCOL is not limited by the UEFI spec. Hence should not allocate a buffer for it on the stack. Signed-off-by:
-
Heinrich Schuchardt authored
The EFI spec does not provide a length limit for variables. Reviewed-by:
-
Heinrich Schuchardt authored
Test printing of Unicode strings Signed-off-by:
-
Heinrich Schuchardt authored
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 authored
Provide unit tests for Unicode functions. Signed-off-by:
-
Heinrich Schuchardt authored
utf8_get() - get next UTF-8 code point from buffer utf8_put() - write UTF-8 code point to buffer utf8_utf16_strnlen() - length of a utf-8 string after conversion to utf-16 utf8_utf16_strncpy() - copy a utf-8 string to utf-16 utf16_get() - get next UTF-16 code point from buffer utf16_put() - write UTF-16 code point to buffer utf16_strnlen() - number of codes points in a utf-16 string utf16_utf8_strnlen() - length of a utf-16 string after conversion to utf-8 utf16_utf8_strncpy() - copy a utf-16 string to utf-8 Signed-off-by:
-
Heinrich Schuchardt authored
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 authored
charset.o is only needed for the EFI subsystem Signed-off-by:
-
Heinrich Schuchardt authored
Using CONFIG_IS_ENABLED(EFI_LOADER) allows to simply the #if statements. Suggested-by:
-
Heinrich Schuchardt authored
Using CONFIG_IS_ENABLED(EFI_LOADER) allows to simply the #if statements. Suggested-by:
-
Alexander Graf authored
The fs_read() function wants to get an address rather than the pointer to a buffer. So let's convert the passed buffer from pointer back a the address to make efi_loader on sandbox happier. Signed-off-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
-
Simon Glass authored
At present this function takes a pointer as its argument, then passes this to efi_allocate_pages(), which actually takes an address. It uses casts, which are not supported on sandbox. Also the function calculates the FDT size rounded up to the neared EFI page size, then its caller recalculates the size and adds a bit more to it. This function is much better written as something that works with addresses only, and returns both the address and the size of the relocated FDT. Also, copy_fdt() returns NULL on error, but really should propagate the error from efi_allocate_pages(). To do this it needs to return an efi_status_t, not a void *. Update the code in this way, so that it is easier to follow, and also supports sandbox. Signed-off-by:
-
Simon Glass authored
Sandbox only has 128MB of memory so we cannot relocate the device tree up to start at 128MB. Use 127MB instead, which should be safe. Signed-off-by:
-
Heinrich Schuchardt authored
Verify that the loaded image protocol is installed on the image handle. Verify that the loaded image protocol points to the system table. Signed-off-by:
-
Heinrich Schuchardt authored
The system table must be passed as a pointer in the loaded image protocol. Signed-off-by:
-
Heinrich Schuchardt authored
Remove memory leak in efi_selftest_manageprotocols.c. Signed-off-by:
-
- Sep 20, 2018
-
-
-
git://git.denx.de/u-boot-marvellTom Rini authored
- Multiples updates to the turris boards / platform - Changes / enhancements to the Marvell PHY drivers, mainly to support the turris platform - Many fixes and enhancements to the pxa3xx NAND driver - Fixes for the UART boot mode in kwboot - Misc minor changes to other 32bit and 64bit boards
-
- Sep 19, 2018
-
-
The Clearfog SOM can optionally have eMMC installed. Enable support for eMMC boot partitions by default. Signed-off-by:
Baruch Siach <baruch@tkos.co.il> Signed-off-by:
Stefan Roese <sr@denx.de>
-
This patch adds support to Armada 7k/8k comphy RX/TX lane swap. The 'phy-invert' DT property defines the inverted signals. Signed-off-by:
Rabeeh Khoury <rabeeh@solid-run.com> Signed-off-by:
-
Exclude mvebu commands from SPL builds Signed-off-by:
Konstantin Porotchkin <kostap@marvell.com> Cc: Igal Liberman <igall@marvell.com> Cc: Stefan Roese <sr@denx.de> Signed-off-by:
-
Add definitions for CONFIG_ENV_SPI_BUS and CONFIG_ENV_SPI_CS to Armada-388-GP board configuration Signed-off-by:
-
For some reason the spi_flash_probe_bus_cs() is called inside the setup_flash_device() with zero values in place of configurated SPI flash mode and maximum flash speed. This code causes HALT error during startup environment relocation on some platforms - namely Armada-38x-GP board. Fix the function call by replacing zeros with the appropriate values - CONFIG_ENV_SPI_MAX_HZ and CONFIG_ENV_SPI_MODE. Signed-off-by:
-
add delay before processing the status flags in pxa3xx_nand_irq(). Signed-off-by:
David Sniatkiwicz <davidsn@marvell.com> Reviewed-by:
Igal Liberman <igall@marvell.com> Reviewed-by:
-
Add support for NAND chips with 8KB page, 4 and 8 bit ECC (ONFI). Signed-off-by:
Ofer Heifetz <oferh@marvell.com> Cc: Stefan Roese <sr@denx.de> Cc: Simon Glass <sjg@chromium.org> Signed-off-by:
-
Add comments with timing parameter names and some details about nand layout fileds. Remove unneeded definition. Signed-off-by:
-
Replace the hardcoded value of page chink with value that depends on flash page size and ECC strength. This fixes nand access errors for 2K page flashes with 8-bit ECC. Move the initial flash commannd function assignment past the ECC structures initialization for eliminating usage of hardcoded page chunk size value. Signed-off-by:
-
Add timings and device ID for Toshiba TC58NVG1S3HTA00 flash Signed-off-by:
-
Add support for 2KB page 8-bit ECC strength flash layout Signed-off-by:
Victor Axelrod <victora@marvell.com> Reviewed-by:
-
