[PATCH 5/6] qoriq: new target

[Hauke Mehrtens]

On 8/22/21 1:15 AM, Stijn Tintel wrote:
> Add a new target named "qoriq", that will support boards using PowerPC
> processors from NXP's QorIQ brand.
> 
> This doesn't actually add support for any board yet, so that
> installation instructions can go in the commit message of the commit
> that adds actual support for a board.
> 
> Signed-off-by: Stijn Tintel <stijn at linux-ipv6.be>
> ---
>   target/linux/qoriq/Makefile          |  21 ++
>   target/linux/qoriq/config-5.10       | 414 +++++++++++++++++++++++++++
>   target/linux/qoriq/generic/target.mk |   3 +
>   target/linux/qoriq/image/Makefile    |  34 +++
>   target/linux/qoriq/image/generic.mk  |   0
>   5 files changed, 472 insertions(+)
>   create mode 100644 target/linux/qoriq/Makefile
>   create mode 100644 target/linux/qoriq/config-5.10
>   create mode 100644 target/linux/qoriq/generic/target.mk
>   create mode 100644 target/linux/qoriq/image/Makefile
>   create mode 100644 target/linux/qoriq/image/generic.mk
> 
> diff --git a/target/linux/qoriq/Makefile b/target/linux/qoriq/Makefile
> new file mode 100644
> index 0000000000..d9a9f4d226
> --- /dev/null
> +++ b/target/linux/qoriq/Makefile
> @@ -0,0 +1,21 @@
> +# SPDX-License-Identifier: GPL-2.0-only
> +#
> +# Copyright (C) 2021 Stijn Tintel <stijn at linux-ipv6.be>
> +
> +include $(TOPDIR)/rules.mk
> +
> +ARCH:=powerpc64
> +BOARD:=qoriq
> +BOARDNAME:=NXP QorIQ (PowerPC)
> +CPU_TYPE:=e6500
> +FEATURES:=boot-part ext4 fpu legacy-sdcard powerpc64 ramdisk root-part rtc source-only
> +SUBTARGETS:=generic
> +
> +KERNEL_PATCHVER:=5.10
> +KERNEL_TESTING_PATCHVER:=5.10
> +
> +KERNELNAME:=zImage
> +
> +include $(INCLUDE_DIR)/target.mk
> +
> +$(eval $(call BuildTarget))
> diff --git a/target/linux/qoriq/config-5.10 b/target/linux/qoriq/config-5.10
> new file mode 100644
> index 0000000000..d9d7e9bcf4
> --- /dev/null
> +++ b/target/linux/qoriq/config-5.10
> @@ -0,0 +1,414 @@
....
> +CONFIG_ASN1=y

Why do you need CONFIG_ASN1?

....
> +CONFIG_CRYPTO_AUTHENC=y
> +CONFIG_CRYPTO_CRC32C=y
> +# CONFIG_CRYPTO_CRC32C_VPMSUM is not set
> +CONFIG_CRYPTO_DES=y
> +CONFIG_CRYPTO_DEV_FSL_CAAM=y
> +CONFIG_CRYPTO_DEV_FSL_CAAM_AHASH_API=y
> +CONFIG_CRYPTO_DEV_FSL_CAAM_AHASH_API_DESC=y
> +CONFIG_CRYPTO_DEV_FSL_CAAM_COMMON=y
> +CONFIG_CRYPTO_DEV_FSL_CAAM_CRYPTO_API=y
> +CONFIG_CRYPTO_DEV_FSL_CAAM_CRYPTO_API_DESC=y
> +CONFIG_CRYPTO_DEV_FSL_CAAM_CRYPTO_API_QI=y
> +# CONFIG_CRYPTO_DEV_FSL_CAAM_DEBUG is not set
> +# CONFIG_CRYPTO_DEV_FSL_CAAM_INTC is not set
> +CONFIG_CRYPTO_DEV_FSL_CAAM_JR=y
> +CONFIG_CRYPTO_DEV_FSL_CAAM_PKC_API=y
> +CONFIG_CRYPTO_DEV_FSL_CAAM_RINGSIZE=9
> +CONFIG_CRYPTO_DEV_FSL_CAAM_RNG_API=y
> +# CONFIG_CRYPTO_DEV_NX is not set
> +CONFIG_CRYPTO_ECB=y
> +CONFIG_CRYPTO_ENGINE=y
> +CONFIG_CRYPTO_GF128MUL=y
> +CONFIG_CRYPTO_HW=y
> +CONFIG_CRYPTO_LIB_DES=y
> +CONFIG_CRYPTO_LIB_POLY1305_RSIZE=1
> +# CONFIG_CRYPTO_MD5_PPC is not set
> +CONFIG_CRYPTO_NULL2=y
> +CONFIG_CRYPTO_RNG=y
> +CONFIG_CRYPTO_RNG2=y
> +CONFIG_CRYPTO_RSA=y
> +# CONFIG_CRYPTO_SHA1_PPC is not set
> +CONFIG_CRYPTO_XTS=y

Do you need all this crypto stuff com,piled in or is a module also 
sufficent?

....
> +CONFIG_EXT4_FS=y
> +CONFIG_EXT4_FS_POSIX_ACL=y
> +CONFIG_EXT4_FS_SECURITY=y

CONFIG_EXT4_FS_SECURITY is normally activated by KERNEL_EXT4_FS_SECURITY 
in OpenWrt.

....
> +CONFIG_GCC_PLUGINS=y

Why do you activate CONFIG_GCC_PLUGINS ?

> +# CONFIG_GCC_PLUGIN_CYC_COMPLEXITY is not set
> +# CONFIG_GCC_PLUGIN_LATENT_ENTROPY is not set
> +# CONFIG_GCC_PLUGIN_RANDSTRUCT is not set
> +# CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF is not set
> +# CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL is not set
> +# CONFIG_GCC_PLUGIN_STRUCTLEAK_USER is not set
....
> +# CONFIG_HANGCHECK_TIMER is not set
> +# CONFIG_HARDENED_USERCOPY is not set

CONFIG_HARDENED_USERCOPY should only cause crashes when it detects a 
buffer overflow. Do you have more details about the crashes?

....
> +CONFIG_KGDB=y

Is KGDB needed in the default kernel config?

> +CONFIG_KGDB_HONOUR_BLOCKLIST=y
> +# CONFIG_KGDB_KDB is not set
> +CONFIG_KGDB_SERIAL_CONSOLE=y
> +# CONFIG_KGDB_TESTS is not set
....
> +CONFIG_PTP_1588_CLOCK=y
> +CONFIG_PTP_1588_CLOCK_QORIQ=y

We also have kmod-ptp-qoriq

....

Hauke
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x93DD20630910B515.asc
Type: application/pgp-keys
Size: 13571 bytes
Desc: OpenPGP public key
URL: <http://lists.openwrt.org/pipermail/openwrt-devel/attachments/20210822/6c6d4e09/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openwrt.org/pipermail/openwrt-devel/attachments/20210822/6c6d4e09/attachment.sig>