summaryrefslogtreecommitdiff
path: root/qcom
diff options
context:
space:
mode:
authorDmitry Baryshkov <dmitry.baryshkov@linaro.org>2022-10-11 01:31:10 +0300
committerDmitry Baryshkov <dmitry.baryshkov@linaro.org>2022-10-11 01:31:10 +0300
commit44fa25ddf7d803f347dcdb0ecc52f72268979b92 (patch)
tree661bb13862e231313ed0fbaebfd433bad5297153 /qcom
parentfdf1a65258522edf18a0a1768fbafa61ed07e598 (diff)
downloadlinux-firmware-44fa25ddf7d803f347dcdb0ecc52f72268979b92.tar.gz
qcom: add squashed version of a530 zap shader
Qualcomm binary files can be published in one of two formats: a split MDT+Bnn format, consisting of several files, or a squashed MBN format, consisting of a single ELF file. Most of Qualcomm binary files (except the venus firmware) are distributed (in linux-firmware) and used in the MBN format (even if the original publishing format was MDT), since that requires transfer of a single file between the userspace and the kernel. Provide a squashed variant of Qualcomm Adreno a530 ZAP shader. For backwards compatibility reason the split a530_zap.* files are retained. They can be removed later, after all users migrate to new file location. Cc: Rob Clark <robdclark@chromium.org> Cc: Bjorn Andersson <andersson@kernel.org> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Diffstat (limited to 'qcom')
-rw-r--r--qcom/apq8096/a530_zap.mbnbin0 -> 17188 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/qcom/apq8096/a530_zap.mbn b/qcom/apq8096/a530_zap.mbn
new file mode 100644
index 0000000..2953c4d
--- /dev/null
+++ b/qcom/apq8096/a530_zap.mbn
Binary files differ