cf8e865810
The Itanium architecture is obsolete, and an informal survey [0] reveals that any residual use of Itanium hardware in production is mostly HP-UX or OpenVMS based. The use of Linux on Itanium appears to be limited to enthusiasts that occasionally boot a fresh Linux kernel to see whether things are still working as intended, and perhaps to churn out some distro packages that are rarely used in practice. None of the original companies behind Itanium still produce or support any hardware or software for the architecture, and it is listed as 'Orphaned' in the MAINTAINERS file, as apparently, none of the engineers that contributed on behalf of those companies (nor anyone else, for that matter) have been willing to support or maintain the architecture upstream or even be responsible for applying the odd fix. The Intel firmware team removed all IA-64 support from the Tianocore/EDK2 reference implementation of EFI in 2018. (Itanium is the original architecture for which EFI was developed, and the way Linux supports it deviates significantly from other architectures.) Some distros, such as Debian and Gentoo, still maintain [unofficial] ia64 ports, but many have dropped support years ago. While the argument is being made [1] that there is a 'for the common good' angle to being able to build and run existing projects such as the Grid Community Toolkit [2] on Itanium for interoperability testing, the fact remains that none of those projects are known to be deployed on Linux/ia64, and very few people actually have access to such a system in the first place. Even if there were ways imaginable in which Linux/ia64 could be put to good use today, what matters is whether anyone is actually doing that, and this does not appear to be the case. There are no emulators widely available, and so boot testing Itanium is generally infeasible for ordinary contributors. GCC still supports IA-64 but its compile farm [3] no longer has any IA-64 machines. GLIBC would like to get rid of IA-64 [4] too because it would permit some overdue code cleanups. In summary, the benefits to the ecosystem of having IA-64 be part of it are mostly theoretical, whereas the maintenance overhead of keeping it supported is real. So let's rip off the band aid, and remove the IA-64 arch code entirely. This follows the timeline proposed by the Debian/ia64 maintainer [5], which removes support in a controlled manner, leaving IA-64 in a known good state in the most recent LTS release. Other projects will follow once the kernel support is removed. [0] https://lore.kernel.org/all/CAMj1kXFCMh_578jniKpUtx_j8ByHnt=s7S+yQ+vGbKt9ud7+kQ@mail.gmail.com/ [1] https://lore.kernel.org/all/0075883c-7c51-00f5-2c2d-5119c1820410@web.de/ [2] https://gridcf.org/gct-docs/latest/index.html [3] https://cfarm.tetaneutral.net/machines/list/ [4] https://lore.kernel.org/all/87bkiilpc4.fsf@mid.deneb.enyo.de/ [5] https://lore.kernel.org/all/ff58a3e76e5102c94bb5946d99187b358def688a.camel@physik.fu-berlin.de/ Acked-by: Tony Luck <tony.luck@intel.com> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
121 lines
3.6 KiB
Plaintext
121 lines
3.6 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0-only
|
|
#
|
|
# Platform drivers
|
|
|
|
config CEC_CROS_EC
|
|
tristate "ChromeOS EC CEC driver"
|
|
depends on CROS_EC
|
|
select CEC_CORE
|
|
select CEC_NOTIFIER
|
|
select CROS_EC_PROTO
|
|
help
|
|
If you say yes here you will get support for the
|
|
ChromeOS Embedded Controller's CEC.
|
|
The CEC bus is present in the HDMI connector and enables communication
|
|
between compatible devices.
|
|
|
|
config CEC_MESON_AO
|
|
tristate "Amlogic Meson AO CEC driver"
|
|
depends on ARCH_MESON || COMPILE_TEST
|
|
select CEC_CORE
|
|
select CEC_NOTIFIER
|
|
help
|
|
This is a driver for Amlogic Meson SoCs AO CEC interface. It uses the
|
|
generic CEC framework interface.
|
|
CEC bus is present in the HDMI connector and enables communication
|
|
|
|
config CEC_MESON_G12A_AO
|
|
tristate "Amlogic Meson G12A AO CEC driver"
|
|
depends on ARCH_MESON || COMPILE_TEST
|
|
depends on COMMON_CLK && OF
|
|
select REGMAP
|
|
select REGMAP_MMIO
|
|
select CEC_CORE
|
|
select CEC_NOTIFIER
|
|
help
|
|
This is a driver for Amlogic Meson G12A SoCs AO CEC interface.
|
|
This driver if for the new AO-CEC module found in G12A SoCs,
|
|
usually named AO_CEC_B in documentation.
|
|
It uses the generic CEC framework interface.
|
|
CEC bus is present in the HDMI connector and enables communication
|
|
between compatible devices.
|
|
|
|
config CEC_GPIO
|
|
tristate "Generic GPIO-based CEC driver"
|
|
depends on PREEMPTION || COMPILE_TEST
|
|
select CEC_CORE
|
|
select CEC_PIN
|
|
select CEC_NOTIFIER
|
|
select GPIOLIB
|
|
help
|
|
This is a generic GPIO-based CEC driver.
|
|
The CEC bus is present in the HDMI connector and enables communication
|
|
between compatible devices.
|
|
|
|
config CEC_SAMSUNG_S5P
|
|
tristate "Samsung S5P CEC driver"
|
|
depends on ARCH_EXYNOS || COMPILE_TEST
|
|
select CEC_CORE
|
|
select CEC_NOTIFIER
|
|
help
|
|
This is a driver for Samsung S5P HDMI CEC interface. It uses the
|
|
generic CEC framework interface.
|
|
CEC bus is present in the HDMI connector and enables communication
|
|
between compatible devices.
|
|
|
|
config CEC_STI
|
|
tristate "STMicroelectronics STiH4xx HDMI CEC driver"
|
|
depends on ARCH_STI || COMPILE_TEST
|
|
select CEC_CORE
|
|
select CEC_NOTIFIER
|
|
help
|
|
This is a driver for STIH4xx HDMI CEC interface. It uses the
|
|
generic CEC framework interface.
|
|
CEC bus is present in the HDMI connector and enables communication
|
|
between compatible devices.
|
|
|
|
config CEC_STM32
|
|
tristate "STMicroelectronics STM32 HDMI CEC driver"
|
|
depends on ARCH_STM32 || COMPILE_TEST
|
|
select REGMAP
|
|
select REGMAP_MMIO
|
|
select CEC_CORE
|
|
help
|
|
This is a driver for STM32 interface. It uses the
|
|
generic CEC framework interface.
|
|
CEC bus is present in the HDMI connector and enables communication
|
|
between compatible devices.
|
|
|
|
config CEC_TEGRA
|
|
tristate "Tegra HDMI CEC driver"
|
|
depends on ARCH_TEGRA || COMPILE_TEST
|
|
select CEC_CORE
|
|
select CEC_NOTIFIER
|
|
help
|
|
This is a driver for the Tegra HDMI CEC interface. It uses the
|
|
generic CEC framework interface.
|
|
The CEC bus is present in the HDMI connector and enables communication
|
|
between compatible devices.
|
|
|
|
config CEC_SECO
|
|
tristate "SECO Boards HDMI CEC driver"
|
|
depends on X86 || COMPILE_TEST
|
|
depends on PCI && DMI
|
|
select CEC_CORE
|
|
select CEC_NOTIFIER
|
|
help
|
|
This is a driver for SECO Boards integrated CEC interface.
|
|
Selecting it will enable support for this device.
|
|
CEC bus is present in the HDMI connector and enables communication
|
|
between compatible devices.
|
|
|
|
config CEC_SECO_RC
|
|
bool "SECO Boards IR RC5 support"
|
|
depends on CEC_SECO
|
|
depends on RC_CORE=y || RC_CORE = CEC_SECO
|
|
help
|
|
If you say yes here you will get support for the
|
|
SECO Boards Consumer-IR in seco-cec driver.
|
|
The embedded controller supports RC5 protocol only, default mapping
|
|
is set to rc-hauppauge.
|