From mboxrd@z Thu Jan  1 00:00:00 1970
From: Simon Glass <sjg@chromium.org>
Date: Thu, 15 Oct 2020 09:05:34 -0600
Subject: [PATCH v3 2/2] spl: fdt: Record load/entry fit-images entries in
 64bit format
In-Reply-To: <96f941c67199250db9dc07bf78212f9e834b0237.1602489072.git.michal.simek@xilinx.com>
References: <cover.1602489072.git.michal.simek@xilinx.com>
 <96f941c67199250db9dc07bf78212f9e834b0237.1602489072.git.michal.simek@xilinx.com>
Message-ID: <CAPnjgZ2Xi4HGj-DtO6OZ2pxf3bjyLRoZx2N2RJ7Jjyr=e3KZcw@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Mon, 12 Oct 2020 at 01:51, Michal Simek <michal.simek@xilinx.com> wrote:
>
> The commit 9f45aeb93727 ("spl: fit: implement fdt_record_loadable") which
> introduced fdt_record_loadable() state there spl_fit.c is not 64bit safe.
> Based on my tests on Xilinx ZynqMP zcu102 platform there shouldn't be a
> problem to record these addresses in 64bit format.
> The patch adds support for systems which need to load images above 4GB.
>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> ---
>
> (no changes since v1)
>
>  common/fdt_support.c | 9 ++-------
>  1 file changed, 2 insertions(+), 7 deletions(-)

Reviewed-by: Simon Glass <sjg@chromium.org>

I am wondering whether we should use #size-cells etc. to select this?