db6206136a
tools/fiptool: Fix UUID parsing in blob handling
Commit 0336486 ("Make TF UUID RFC 4122 compliant") changed the scanf
parsing string to handle endianness correctly.
However that changed the number of items sscanf handles, without
adjusting the sanity check just below.
Increase the expected return value from 11 to 16 to let fiptool handle
UUIDs given as blob parameters correctly again.
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
8 lines
580 B
Text
8 lines
580 B
Text
$NetBSD: distinfo,v 1.3 2019/05/14 04:08:51 thorpej Exp $
|
|
|
|
SHA1 (arm-trusted-firmware-2.0.zip) = d789e7aac0e987d8524a11587cc598bf5d894581
|
|
RMD160 (arm-trusted-firmware-2.0.zip) = a7a49da9b0e27c45df867ea1de4809cb89d9b8cc
|
|
SHA512 (arm-trusted-firmware-2.0.zip) = 39180d12be7532b742949f162759793e97c0a6ac835d66aaf857bd3c1d9c0ab10b7ccd5e6a47831ad909a92b4727e181c82a74c90b5d941e469f3a5cf66b0e7c
|
|
Size (arm-trusted-firmware-2.0.zip) = 3949049 bytes
|
|
SHA1 (patch-Makefile) = b5c27e44135e6a99c1a598daec91db58d6ff894d
|
|
SHA1 (patch-fiptool_uuid_parse) = 6ef5785e2f696e0297239cb597b94dd3ac4a6c7d
|