u-boot.git/lib, branch u-boot-2016.09.y

efi_loader: provide efi_mem_desc version

2016-09-07T12:49:07+00:00

Provide version of struct efi_mem_desc in efi_get_memory_map().

EFI_BOOT_SERVICES.GetMemoryMap() in UEFI specification v2.6 defines
memory descriptor version to 1. Linux kernel also expects descriptor
version to be 1 and prints following warning during boot if its not:

Unexpected EFI_MEMORY_DESCRIPTOR version 0

Signed-off-by: Mian Yousaf Kaukab

x86: efi: payload: Make EFI payload build again

2016-08-30T01:26:05+00:00

Since commit 73c5c39 "Makefile: Drop unnecessary -dtb suffixes",
EFI payload does not build anymore. This fixes the build.

Signed-off-by: Bin Meng 
Reviewed-by: Simon Glass

efi_loader: Fix relocations above 64kb image size

2016-08-20T18:03:27+00:00

We were truncating the image offset within the target image to 16 bits
which again meant that we were potentially overwriting random memory
in the lower 16 bits of the image.

This patch casts the offset to a more reasonable 32bits.

With this applied, I can successfully see Shell.efi assert because it
can't find a protocol it expects to be available.

Signed-off-by: Alexander Graf

tests: Introduce DT overlay tests

2016-08-20T15:35:07+00:00

This adds a bunch of unit tests for the "fdt apply" command.

They've all been run successfully in the sandbox. However, as you still
require an out-of-tree dtc with overlay support, this is disabled by
default.

Acked-by: Simon Glass 
Acked-by: Pantelis Antoniou 
Signed-off-by: Maxime Ripard

cmd: fdt: add fdt overlay application subcommand

2016-08-20T15:35:05+00:00

The device tree overlays are a good way to deal with user-modifyable
boards or boards with some kind of an expansion mechanism where we can
easily plug new board in (like the BBB or the raspberry pi).

However, so far, the usual mechanism to deal with it was to have in Linux
some driver detecting the expansion boards plugged in and then request
these overlays using the firmware interface.

That works in most cases, but in some cases, you might want to have the
overlays applied before the userspace comes in. Either because the new
board requires some kind of an early initialization, or because your root
filesystem is accessed through that expansion board.

The easiest solution in such a case is to simply have the component before
Linux applying that overlay, removing all these drawbacks.

Reviewed-by: Stefan Agner 
Acked-by: Pantelis Antoniou 
Acked-by: Simon Glass 
Signed-off-by: Maxime Ripard

libfdt: Add overlay application function

2016-08-20T15:35:04+00:00

The device tree overlays are a good way to deal with user-modifyable
boards or boards with some kind of an expansion mechanism where we can
easily plug new board in (like the BBB, the Raspberry Pi or the CHIP).

Add a new function to merge overlays with a base device tree.

Signed-off-by: Maxime Ripard

libfdt: Add fdt_setprop_inplace_namelen_partial

2016-08-20T15:35:04+00:00

Add a function to modify inplace only a portion of a property..

This is especially useful when the property is an array of values, and you
want to update one of them without changing the DT size.

Signed-off-by: Maxime Ripard 
Acked-by: Simon Glass

libfdt: Add fdt_path_offset_namelen

2016-08-20T15:35:02+00:00

Add a namelen variant of fdt_path_offset to retrieve the node offset using
only a fixed number of characters.

Reviewed-by: Simon Glass 
Signed-off-by: Maxime Ripard

libfdt: Fix separator spelling

2016-08-20T15:35:02+00:00

The function fdt_path_next_seperator had an obvious mispell. Fix it.

Signed-off-by: Maxime Ripard

libfdt: Add max phandle retrieval function

2016-08-20T15:35:01+00:00

Add a function to retrieve the highest phandle in a given device tree.

Signed-off-by: Maxime Ripard 
Reviewed-by: Stefan Agner 
Acked-by: Simon Glass