lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2ce5cd86-ed0d-3e5f-2ab4-717e055dfef4@huawei.com>
Date:   Wed, 4 Aug 2021 16:51:01 +0800
From:   Zenghui Yu <yuzenghui@...wei.com>
To:     Arnd Bergmann <arnd@...nel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>, <soc@...nel.org>
CC:     Jun Nie <jun.nie@...aro.org>, Shawn Guo <shawnguo@...nel.org>,
        "Arnd Bergmann" <arnd@...db.de>
Subject: Re: [PATCH 3/5] ARM: remove zte zx platform

On 2021/1/20 20:48, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@...db.de>
> 
> The ZTE ZX set-top-box SoC platform was added in 2015 by Jun Nie, with
> Baoyou Xie and Shawn Guo subsequently becoming maintainers after the
> addition of the 64-bit variant.
> 
> However, the only machines that were ever supported upstream are the
> reference designs, not actual set-top-box devices that would benefit
> from this support. All ZTE set-top-boxes from the past few years seem
> to be based on third-party SoCs. While there is very little information
> about zx296702 and zx296718 on the web, I found some references to other
> chips from the same family, such as zx296716 and zx296719, which were
> never submitted for upstream support. Finally, there is no support for
> the GPU on either of them, with the lima and panfrost device drivers
> having been added after work on the zx platform had stopped.
> 
> Shawn confirmed that he has not seen any interest in this platform for
> the past four years, and that it can be removed.
> 
> Thanks to Jun and Shawn for maintaining this platform over the past
> five years.
> 
> Cc: Jun Nie <jun.nie@...aro.org>
> Cc: Shawn Guo <shawnguo@...nel.org>
> Signed-off-by: Arnd Bergmann <arnd@...db.de>

[...]

> diff --git a/MAINTAINERS b/MAINTAINERS
> index aeef69cbc7ec..54b5e6dee017 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2704,40 +2704,6 @@ S:	Maintained
>  F:	arch/arm/mach-pxa/include/mach/z2.h
>  F:	arch/arm/mach-pxa/z2.c
>   
> -ARM/ZTE ARCHITECTURE
> -M:	Jun Nie <jun.nie@...aro.org>
> -M:	Shawn Guo <shawnguo@...nel.org>
> -L:	linux-arm-kernel@...ts.infradead.org (moderated for non-subscribers)
> -S:	Maintained

[...]

> -F:	include/dt-bindings/clock/zx2967*.h

include/dt-bindings/clock/zx296718-clock.h hadn't been removed.

> -F:	include/dt-bindings/soc/zte,*.h

include/dt-bindings/soc/zte,pm_domains.h neither.

> -DRM DRIVERS FOR ZTE ZX
> -M:	Shawn Guo <shawnguo@...nel.org>
> -L:	dri-devel@...ts.freedesktop.org
> -S:	Maintained
> -T:	git git://anongit.freedesktop.org/drm/drm-misc
> -F:	Documentation/devicetree/bindings/display/zte,vou.txt
> -F:	drivers/gpu/drm/zte/

The whole zxdrm driver is still in tree, which smells like a leftover.

> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> index 6eecdef538bd..ec3c0cb27d1e 100644
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -317,12 +317,6 @@ config ARCH_XGENE
>  	help
>  	  This enables support for AppliedMicro X-Gene SOC Family
>  
> -config ARCH_ZX
> -	bool "ZTE ZX SoC Family"
> -	select PINCTRL
> -	help
> -	  This enables support for ZTE ZX SoC Family

And ARCH_ZX is still selected in arm64's defconfig (which is why I
jumped in this series).

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ