~tobetter/+git/u-boot:u-boot_v2018.03

Last commit made on 2018-04-25
Get this branch:
git clone -b u-boot_v2018.03 https://git.launchpad.net/~tobetter/+git/u-boot

Branch merges

Branch information

Name:
u-boot_v2018.03
Repository:
lp:~tobetter/+git/u-boot

Recent commits

cfb0df6... by Dongjin Kim

ODROID: add debian packagin scripts

Change-Id: I8c49aa9f31f25874fdf3c3be4da7308c87cf24cb
Signed-off-by: Dongjin Kim <email address hidden>

9d20940... by Dongjin Kim

ODROID: fix reversed partition for U-boot image and TZ firmware

Signed-off-by: Dongjin Kim <email address hidden>

e79de69... by Dongjin Kim

ODROID: XU3/4: add prebuilt binaries

Change-Id: I95297c30440c5a3d565a935048ba854fd00fd188
Signed-off-by: Dongjin Kim <email address hidden>

70fdfa4... by Dongjin Kim

ODROID: C2: add prebuilt binaries and signing tools

For Hardkernel's ODROID-C2, 'u-boot.bin' have to be composed with prebuilt
binaries from AMLogic by 'fip_create' and be signed with a tool
'aml_encrypt_gxbb'. Since the source file of 'aml_encrypt_gxbb' is not
provided by AMLogic, 'amlbootsign' developed by 'Andreas Färber' can be used
for signing. Both source codes are ported to U-boot source tree in
'tools/amlogic'.

'https://github.com/afaerber/meson-tools' is the repository for the original
source files of 'amlbootsign' and have been tested with ODROID-C2 only.

The flashing image for U-boot 'u-boot.bin.signed' is finally built in
'board/amlogic/odroid-c2/bin' and can be flashed with a script 'sd_fusing.sh'
in the same directory.

 $ cd board/amlogic/odroid-c2/bin
 $ sudo ./sd_fusing.sh <your/memory/card/device>

Change-Id: I33f3f6b9956901839ff78db545a1f169bfee81bf
Signed-off-by: Dongjin Kim <email address hidden>

f95ab1f... by Tom Rini <email address hidden>

Prepare v2018.03

Signed-off-by: Tom Rini <email address hidden>

ca89df7... by Bryan O'Donoghue <email address hidden>

imx: hab: Convert DCD non-NULL error to warning

commit 8c4037a09a5c ("imx: hab: Ensure the IVT DCD pointer is Null prior
to calling HAB authenticate function.") makes the DCD field being NULL a
dependency.

This change though will break loading and executing of existing pre-signed
binaries on a u-boot update i.e. if this change is deployed on a board you
will be forced to redo all images on that board to NULL out the DCD.

There is no prior guidance from NXP that the DCD must be NULL similarly
public guidance on usage of the HAB doesn't call out this NULL dependency
(see boundary devices link).

Since later SoCs will reject a non-NULL DCD there's no reason to make a
NULL DCD a requirement, however if there is an actual dependency for later
SoCs the appropriate fix would be to do SoC version checking.

Earlier SoCs are capable (and happy) to authenticate images with non-NULL
DCDs, we should not be forcing this change on downstream users -
particularly if it means those users now must rewrite their build systems
and/or redeploy signed images in the field.

Fixes: 8c4037a09a5c ("imx: hab: Ensure the IVT DCD pointer is Null prior
to calling HAB authenticate function.")

Signed-off-by: Bryan O'Donoghue <email address hidden>
Cc: Utkarsh Gupta <email address hidden>
Cc: Breno Lima <email address hidden>
Cc: Fabio Estevam <email address hidden>
Link: https://boundarydevices.com/high-assurance-boot-hab-dummies
Reviewed-by: Fabio Estevam <email address hidden>

6d7403b... by Breno Lima <email address hidden>

doc: mxc_hab: Update i.MX HAB documentation

The README.mxc_hab is outdated and need improvements, add the following
modifications:

- Reorganize document and remove duplicate content
- Add CST download link
- Update CST package name
- Align command lines with CST v2.3.3
- Update U-Boot binary name
- Remove CSF padding since is not documented in AN4581

Signed-off-by: Breno Lima <email address hidden>

b887f0a... by Breno Lima <email address hidden>

doc: mxc_hab: Move HAB related info to the appropriate doc

Currently the High Assurance Boot procedure is documented in two
places:

- doc/README.imx6
- doc/README.mxc_hab

It is better to consolidate all HAB related information into
README.mxc_hab file, so move the content from README.imx6 to
README.mxc_hab.

Signed-off-by: Breno Lima <email address hidden>
Reviewed-by: Fabio Estevam <email address hidden>

f0d5bd4... by Bryan O'Donoghue <email address hidden>

imx: hab: Make usage of packed attribute consistent

commit cd2d46003ce1 ("arm: imx: hab: Add IVT header definitions") declares
struct ivt_header as "__attribute__((packed))".

commit ed286bc80e9d ("imx: hab: Check if CSF is valid before
authenticating image") declares struct hab_hdr with __packed.

This patch makes the __packed convention consistent.

Signed-off-by: Bryan O'Donoghue <email address hidden>
Cc: Utkarsh Gupta <email address hidden>
Cc: Breno Lima <email address hidden>
Cc: Fabio Estevam <email address hidden>
Reviewed-by: Fabio Estevam <email address hidden>

ffab61f... by Bryan O'Donoghue <email address hidden>

imx: hab: Fix usage of packed attribute

commit ed286bc80e9d ("imx: hab: Check if CSF is valid before authenticating
image") makes use of "__packed" as a prefix to the "struct hab_hdr"
declaration.

With my compiler "gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)" we
get:

./arch/arm/include/asm/mach-imx/hab.h:42:25: error: expected ‘=’, ‘,’, ‘;’,
‘asm’ or ‘__attribute__’ before ‘{’ token
 struct __packed hab_hdr {

Fix this problem by including <linux/compiler.h>

Signed-off-by: Bryan O'Donoghue <email address hidden>
Cc: Utkarsh Gupta <email address hidden>
Cc: Breno Lima <email address hidden>
Cc: Fabio Estevam <email address hidden>
Reviewed-by: Fabio Estevam <email address hidden>