public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Kever Yang <kever.yang@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] How to support ATF on u-boot
Date: Thu, 14 Jul 2016 10:07:09 +0800	[thread overview]
Message-ID: <5786F3CD.1030808@rock-chips.com> (raw)
In-Reply-To: <36bb7650-5ea3-3d12-6134-4ef32b517cc7@suse.de>

Hi Andreas,

On 07/13/2016 08:27 PM, Andreas F?rber wrote:
> Hi Kever,
>
> Am 20.06.2016 um 04:59 schrieb Kever Yang:
>>      I want to upstream a new SoC named RK3399 from Rockchip which is
>> AARCH64/ARMv8, we need to support Arm Trust Firmware base on U-boot.
>>
>>      Right now we are using a miniloader(just like SPL in U-boot) to load
>> ATF/U-boot,
>> and PC jump from miniloader to ATF and then to U-boot(with CPU change to
>> EL2 mode or nsEL1),
>> then U-boot load kernel/rootfs as usual.
>>
>>      The ATF support for RK3399 has already upstream
>>      Could you give your opinion on how to support ATF on U-boot upstream?
>> When I asked Simon Glass offline, he suggest if we can build ATF as part
>> of the
>> U-boot build process, perhaps with a script in U-boot tree,
>>
>> Perhaps something like:
>>
>> make rk3399_board_defconfig
>> make
>> ./scripts/build-atf-image rk3399_board
>> ^^ new script
>>
>> In any case, a good README would help.
> I've started looking into RK3368 for my GeekBox, which raises a similar
> issue. Are you working on that as well or just RK3399?
I'm working on RK3399 platform now, but the rk3368 should be the same.
>
> Personally I think that the approach the HiKey has taken is the best,
> i.e. decouple U-Boot from ATF and just supply a README for how to make
> it work with U-Boot as ATF payload.
Yes, I'm cleaning a patchset just like HiKey with a readme to support ATF,
but in Rockchip way and Rockchip tools.
>
> Obviously it would help to integrate your loaderimage tool into mkimage.
For the loaderimage integrate into mkimage, I think it depends on if we need
the Rockchip miniloader in the future. If the SPL support the package 
and parse
multi image including ATF, then we can use everyting from U-boot.
>
> Also, what is the difference between your trust_merger tool and ATF's
> fip_create / fiptool?
I didn't look into ATF's fip_create/fiptool so far, the trust_merger 
tool is to package
the  ATF binary/binaries in format for Rockchip miniloader.

Thanks,
- Kever
>
> Regards,
> Andreas
>

      parent reply	other threads:[~2016-07-14  2:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20  2:59 [U-Boot] How to support ATF on u-boot Kever Yang
2016-07-12 19:35 ` Simon Glass
2016-07-13 12:27 ` Andreas Färber
2016-07-13 12:45   ` Andre Przywara
2016-07-13 13:25     ` Andreas Färber
2016-07-13 13:42       ` Andre Przywara
2016-07-14 12:14     ` Kever Yang
2016-07-26 23:42       ` Simon Glass
2016-07-14  2:07   ` Kever Yang [this message]

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=5786F3CD.1030808@rock-chips.com \
    --to=kever.yang@rock-chips.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