arm-trusted-firmware/bl1
Roberto Vargas 033648652f Make TF UUID RFC 4122 compliant
RFC4122 defines that fields are stored in network order (big endian),
but TF-A stores them in machine order (little endian by default in TF-A).
We cannot change the future UUIDs that are already generated, but we can store
all the bytes using arrays and modify fiptool to generate the UUIDs with
the correct byte order.

Change-Id: I97be2d3168d91f4dee7ccfafc533ea55ff33e46f
Signed-off-by: Roberto Vargas <roberto.vargas@arm.com>
2018-06-14 14:41:00 +01:00
..
aarch32 Rename 'smcc' to 'smccc' 2018-03-21 10:49:27 +00:00
aarch64 Rename 'smcc' to 'smccc' 2018-03-21 10:49:27 +00:00
tbbr Fix MISRA rule 8.4 Part 4 2018-04-13 14:01:56 +01:00
bl1.ld.S Add comments about mismatched TCR_ELx and xlat tables 2018-02-27 09:55:01 +00:00
bl1.mk bl2-el3: Don't compile BL1 when BL2_AT_EL3 is defined in FVP 2018-01-18 16:25:18 +00:00
bl1_fwu.c Fix MISRA rule 8.3 Part 4 2018-04-13 14:01:56 +01:00
bl1_main.c Make TF UUID RFC 4122 compliant 2018-06-14 14:41:00 +01:00
bl1_private.h Clean usage of void pointers to access symbols 2018-03-27 13:20:27 +01:00