kumquat-buildroot/package/optee-examples/Config.in
Thomas Petazzoni f7a316e0fb package/optee-client: add dependency on headers >= 4.3
Since upstream commit 5da4da99e0bb3d694e93046207ae4ce3b5545043, in
3.13.0, OP-TEE client unconditionally uses the MMC_IOC_MULTI_CMD
ioctl(). But this ioctl() was only introduced in kernel 4.3, so
earlier kernels did not have this definition.

This was clearly known when upstream started using this ioctl. From
the upstream commit 5da4da99e0bb3d694e93046207ae4ce3b5545043 commit
log:

    As MMC_IOC_MULTI_CMD is available since linux 4.3, we should be safe to
    use it by default on read / write block operations.

So let's propagate this dependency into Buildroot.

Fixes:

  http://autobuild.buildroot.net/results/bd270a6793df499d5f52959e3de17f8a92d88305/

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-08-02 22:09:11 +02:00

27 lines
1.1 KiB
Plaintext

config BR2_PACKAGE_OPTEE_EXAMPLES
bool "optee-examples"
depends on BR2_TARGET_OPTEE_OS
depends on BR2_TOOLCHAIN_HAS_THREADS # optee-client
depends on !BR2_STATIC_LIBS # optee-client
depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_3 # optee-client
select BR2_PACKAGE_OPTEE_CLIENT
select BR2_TARGET_OPTEE_OS_SDK
help
Enable the OP-TEE examples package that brings examples of
implementation of OP-TEE non-secure client applications and
secure trusted applications. OP-TEE examples is a
component delivered by the OP-TEE project.
Trusted application binary files are installed in the target
directory /lib/optee_armtz as other trusted applications.
At runtime OP-TEE OS can load trusted applications from this
non-secure filesystem/directory into the secure world for
execution.
https://github.com/linaro-swg/optee_examples
comment "optee-examples needs a toolchain w/ threads, dynamic library, headers >= 4.3"
depends on BR2_TARGET_OPTEE_OS
depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS || \
!BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_3