From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Simek Date: Mon, 7 Sep 2020 11:00:46 +0200 Subject: [PATCH 0/2] Add support for loading images above 4GB In-Reply-To: References: <9fea7123-e08c-7cf2-ddb6-5664f9f6446f@gmx.de> <251f2fa5-5c34-b221-21f2-9ea894494ada@xilinx.com> Message-ID: <319d3b82-cd79-8e7c-d1dd-c49ca4587c76@xilinx.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Simon, On 07. 09. 20 3:43, Simon Glass wrote: > Hi Michal, > > On Thu, 3 Sep 2020 at 06:30, Michal Simek wrote: >> >> Hi, >> >> On 03. 09. 20 13:16, Heinrich Schuchardt wrote: >>> On 9/3/20 1:03 PM, Michal Simek wrote: >>>> Hi, >>>> >>>> We have several use cases where customers want to partition memory by >>>> putting NS images above 4GB. On Xilinx arm 64bit SOC 0-2GB can be used for >>>> others CPU in the systems (like R5) or for secure sw. >>>> Currently there is limitation in SPL to record load/entry addresses in >>>> 64bit format because they are recorded in 32bit only. >>>> This series add support for it. >>>> Patches have been tested on Xilinx ZynqMP zcu102 board in SD bootmode with >>>> images generated by binman. Because u-boot is using >>>> CONFIG_POSITION_INDEPENDENT it can be put to others 4k aligned addresses >>>> and there is no real need to build it to certain offset. >>>> >>>> Thanks, >>>> Michal >>> >>> Hello Michal, >>> >>> does this series require changes to doc/uImage.FIT/source_file_format.txt? >> >> I am not changing fit format. I am just changing how SPL records >> loadables in DT fit-images node. And also series is using FIT functions >> for reading these properties (at least in this version). > > Well I think there should be some mention of the 32/64 bit issue added > to the FIT docs. How about adding an example with 64-bit addresses? git grep "fit-images" doc/ and output is 0. It means we really don't have any documentation for fit-images embed node. It means we should create one. /fit-images are related to loadables property that's why I think make sense to document them together. What about doc/uImage.FIT/howto.txt? Thanks, Michal Do we have any doc which describe