From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/2] Add support for loading images above 4GB
Date: Mon, 7 Sep 2020 11:00:46 +0200 [thread overview]
Message-ID: <319d3b82-cd79-8e7c-d1dd-c49ca4587c76@xilinx.com> (raw)
In-Reply-To: <CAPnjgZ2S1dYkY7w4pi85s1p81EL1S+3HPtLjEtxy1+itsJgOKQ@mail.gmail.com>
Hi Simon,
On 07. 09. 20 3:43, Simon Glass wrote:
> Hi Michal,
>
> On Thu, 3 Sep 2020 at 06:30, Michal Simek <michal.simek@xilinx.com> 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
next prev parent reply other threads:[~2020-09-07 9:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 11:03 [PATCH 0/2] Add support for loading images above 4GB Michal Simek
2020-09-03 11:03 ` [PATCH 1/2] spl: Use standard FIT entries Michal Simek
2020-09-07 1:43 ` Simon Glass
2020-09-07 8:27 ` Michal Simek
2020-09-07 13:57 ` Simon Glass
2020-09-03 11:03 ` [PATCH 2/2] spl: fdt: Record load/entry fit-images entries in 64bit format Michal Simek
2020-09-07 1:43 ` Simon Glass
2020-09-07 8:29 ` Michal Simek
2020-09-07 13:57 ` Simon Glass
2020-10-05 8:55 ` Michal Simek
2020-09-07 8:55 ` Michal Simek
2020-09-03 11:16 ` [PATCH 0/2] Add support for loading images above 4GB Heinrich Schuchardt
2020-09-03 12:30 ` Michal Simek
2020-09-07 1:43 ` Simon Glass
2020-09-07 9:00 ` Michal Simek [this message]
2020-09-07 13:57 ` Simon Glass
2020-10-05 8:56 ` Michal Simek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=319d3b82-cd79-8e7c-d1dd-c49ca4587c76@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox