summaryrefslogtreecommitdiffstats
path: root/firmware
diff options
context:
space:
mode:
authorLucas Stach <l.stach@pengutronix.de>2019-01-30 16:48:50 +0100
committerSascha Hauer <s.hauer@pengutronix.de>2019-02-01 07:46:14 +0100
commitab6fe92c7d1f6b7559202a6a3b1f34a2f6236607 (patch)
treebbfd3f7d02d79d33f213f2b5b95242ec681d6cc0 /firmware
parenteebb90255206c1d8461d9ab2914a63a775ef6e2f (diff)
downloadbarebox-ab6fe92c7d1f6b7559202a6a3b1f34a2f6236607.tar.gz
barebox-ab6fe92c7d1f6b7559202a6a3b1f34a2f6236607.tar.xz
firmware: imx: remove prebuilt ATF binary
The prebuilt ATF binary is in fact a license compliance issue. While the used BSD-3-clause license allows aggregation with the Barebox binary, the chosen license requires us to ship the license text itself for the source distribution and also for the binary form if the built boot image contains the ATF binary. As this is a restriction that only applies to some boot images, depending on the Barebox configuration, it's non-trivial to do proper license compliance from within the Barebox source. Remove the prebuilt binary and rely on the external build system or user to provide the correct binary. Most system build systems already provide a proper way to handle the license dependency issue. Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'firmware')
-rwxr-xr-xfirmware/imx/imx8m-bl31.binbin46744 -> 0 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/firmware/imx/imx8m-bl31.bin b/firmware/imx/imx8m-bl31.bin
deleted file mode 100755
index b2310e4334..0000000000
--- a/firmware/imx/imx8m-bl31.bin
+++ /dev/null
Binary files differ