[U-Boot] board/amlogic/odroid-c2/README - how to make the instructions more portable?

[Martin Husemann]

Hi folks,

I am trying to get a new u-boot on my Odroid C2 following the instructions
in board/amlogic/odroid-c2/README.

Unfortunately these tell me to use not only the vendor provided blobs, but
also their tools. This is painfull: 

file $DIR/fip/fip_create
odroid-c2/fip/fip_create: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=0dc4b0e1bd118ffc3c0f77e815b6d86acc1f25c2, not stripped

so I need to set up an environment where I can run that.

There are alternatives, so the instructions should probably be updated to
use them. I have "fiptool" from ARM trusted firmware v2.0, and
"fiptool create" should be able to do what fip_create did. Also I have
meson-tools installed, providing amlbootsig which could replace 
aml_encrypt_gxb.

Has someone used these alternate tools instead of the vendor binaries?
How do the fip_create options from the README translate to fiptool?

Martin