diff options
| author | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2020-02-08 21:58:55 +0100 |
|---|---|---|
| committer | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2020-02-14 14:10:51 +0100 |
| commit | 7d7aa2fd924c27829ec25f825481554dd81bce97 (patch) | |
| tree | 658b87b89331670266163e522ea5fb52535633cb /target/linux/bcm27xx/patches-4.19/950-0248-tpm-Make-SECURITYFS-a-weak-dependency.patch | |
| parent | e7bfda2c243e66a75ff966ba04c28b1590b5d24c (diff) | |
| download | upstream-7d7aa2fd924c27829ec25f825481554dd81bce97.tar.gz upstream-7d7aa2fd924c27829ec25f825481554dd81bce97.tar.bz2 upstream-7d7aa2fd924c27829ec25f825481554dd81bce97.zip | |
brcm2708: rename target to bcm27xx
This change makes the names of Broadcom targets consistent by using
the common notation based on SoC/CPU ID (which is used internally
anyway), bcmXXXX instead of brcmXXXX.
This is even used for target TITLE in make menuconfig already,
only the short target name used brcm so far.
Despite, since subtargets range from bcm2708 to bcm2711, it seems
appropriate to use bcm27xx instead of bcm2708 (again, as already done
for BOARDNAME).
This also renames the packages brcm2708-userland and brcm2708-gpu-fw.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Acked-by: Álvaro Fernández Rojas <noltari@gmail.com>
Diffstat (limited to 'target/linux/bcm27xx/patches-4.19/950-0248-tpm-Make-SECURITYFS-a-weak-dependency.patch')
| -rw-r--r-- | target/linux/bcm27xx/patches-4.19/950-0248-tpm-Make-SECURITYFS-a-weak-dependency.patch | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/target/linux/bcm27xx/patches-4.19/950-0248-tpm-Make-SECURITYFS-a-weak-dependency.patch b/target/linux/bcm27xx/patches-4.19/950-0248-tpm-Make-SECURITYFS-a-weak-dependency.patch new file mode 100644 index 0000000000..7e86b09840 --- /dev/null +++ b/target/linux/bcm27xx/patches-4.19/950-0248-tpm-Make-SECURITYFS-a-weak-dependency.patch @@ -0,0 +1,35 @@ +From 38e82adecd1b7ae790a827c29e954d35a2bbee98 Mon Sep 17 00:00:00 2001 +From: Peter Huewe <peterhuewe@gmx.de> +Date: Mon, 3 Sep 2018 21:51:51 +0200 +Subject: [PATCH] tpm: Make SECURITYFS a weak dependency + +commit 2f7d8dbb11287cbe9da6380ca14ed5d38c9ed91f upstream. + +While having SECURITYFS enabled for the tpm subsystem is beneficial in +most cases, it is not strictly necessary to have it enabled at all. +Especially on platforms without any boot firmware integration of the TPM +(e.g. raspberry pi) it does not add any value for the tpm subsystem, +as there is no eventlog present. + +By turning it from 'select' to 'imply' it still gets selected per +default, but enables users who want to save some kb of ram by turning +SECURITYFS off. + +Signed-off-by: Peter Huewe <peterhuewe@gmx.de> +Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> +Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> +--- + drivers/char/tpm/Kconfig | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +--- a/drivers/char/tpm/Kconfig ++++ b/drivers/char/tpm/Kconfig +@@ -5,7 +5,7 @@ + menuconfig TCG_TPM + tristate "TPM Hardware Support" + depends on HAS_IOMEM +- select SECURITYFS ++ imply SECURITYFS + select CRYPTO + select CRYPTO_HASH_INFO + ---help--- |