(snip non-LAKML CCs)

On 22 May 2015 at 12:35, Catalin Marinas [off-list ref] wrote:

On Mon, May 11, 2015 at 08:41:53AM +0200, Ard Biesheuvel wrote:

quoted

This splits off the reservation of the memory occupied by the FDT
binary itself from the processing of the memory reservations it
contains. This is necessary because the physical address of the FDT,
which is needed to perform the reservation, may not be known to the
FDT driver core, i.e., it may be mapped outside the linear direct
mapping, in which case __pa() returns a bogus value.

Cc: Russell King <redacted>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <redacted>
Acked-by: Rob Herring <robh@kernel.org>
Acked-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Ard Biesheuvel <redacted>

For the arm64 part:

Acked-by: Catalin Marinas <catalin.marinas@arm.com>

Thanks Catalin,

Since there has been virtually no discussion about these patches, I
guess they have missed the window for being considered for inclusion
in v4.2

May I suggest that you at least consider these patches regarding the ID map

http://article.gmane.org/gmane.linux.ports.arm.kernel/411720
http://article.gmane.org/gmane.linux.ports.arm.kernel/411721

since they are self-contained and the first one does fix a potential
problem where the Image placement logic in the stub does not take the
512 MB alignment boundary into account. The second one is a trivial
cleanup.

Perhaps Mark can comment on the desirability to include the FDT
remapping patch (which depends on this 1/8).

http://article.gmane.org/gmane.linux.kernel.efi/5738

I don't have strong preference either way, although it would be good
to get some patches off my personal queue.

Regards,
Ard.