sh64: drop support for architecture
PATCH 1/1 sh64: drop support for architecture
There seems to be no hardware or emulator available for this architecture. Someone from ST Microelectronics told me that sh64/sh5 projects are dropped over ten years ago. I found nothing about real hardware on the sites of Hitachi or Renesas.
We should drop this.
Support in uClibc-ng will be dropped in 1.1.
---
Or does anyone know of any sh64/sh5 hardware?
--- arch/Config.in | 10 +--------- arch/Config.in.sh | 3 +-- linux/Config.in | 6 +++--- package/gdb/Config.in | 4 ++-- package/libunwind/Config.in | 4 ++-- toolchain/toolchain-buildroot/Config.in | 4 ++-- 6 files changed, 11 insertions(+), 20 deletions(-)
arch/Config.in +1 -9
@@ -161,14 +161,6 @@ config BR2_sh http://www.hitachi.com/ http://en.wikipedia.org/wiki/SuperH -config BR2_sh64 - bool "SuperH64" - help - SuperH64 (or SH) is a 64-bit reduced instruction set computer (RISC) - instruction set architecture (ISA) developed by Hitachi. - http://www.hitachi.com/ - http://en.wikipedia.org/wiki/SuperH - config BR2_sparc bool "SPARC" help
@@ -342,7 +334,7 @@ if BR2_powerpc || BR2_powerpc64 || BR2_powerpc64le source "arch/Config.in.powerpc" endif -if BR2_sh || BR2_sh64 +if BR2_sh source "arch/Config.in.sh" endif
arch/Config.in.sh +1 -2
@@ -23,10 +23,9 @@ config BR2_ARCH default "sh4eb" if BR2_sh4eb default "sh4a" if BR2_sh4a default "sh4aeb" if BR2_sh4aeb - default "sh64" if BR2_sh64 config BR2_ENDIAN - default "LITTLE" if BR2_sh4 || BR2_sh4a || BR2_sh64 + default "LITTLE" if BR2_sh4 || BR2_sh4a default "BIG" if BR2_sh2a || BR2_sh4eb || BR2_sh4aeb config BR2_ARCH_HAS_ATOMICS
linux/Config.in +3 -3
@@ -177,7 +177,7 @@ choice config BR2_LINUX_KERNEL_UIMAGE bool "uImage" depends on BR2_arc || BR2_arm || BR2_armeb || BR2_bfin || \ - BR2_powerpc || BR2_sh || BR2_sh64 || \ + BR2_powerpc || BR2_sh || \ BR2_mips || BR2_mipsel || BR2_mips64 || BR2_mips64el select BR2_LINUX_KERNEL_UBOOT_IMAGE
@@ -196,7 +196,7 @@ config BR2_LINUX_KERNEL_ZIMAGE bool "zImage" depends on BR2_arm || BR2_armeb || BR2_powerpc || \ BR2_powerpc64 || BR2_powerpc64le || BR2_sparc || \ - BR2_sh || BR2_sh64 || BR2_xtensa + BR2_sh || BR2_xtensa config BR2_LINUX_KERNEL_APPENDED_ZIMAGE bool "zImage with appended DT"
@@ -225,7 +225,7 @@ config BR2_LINUX_KERNEL_LINUX_BIN config BR2_LINUX_KERNEL_VMLINUX_BIN bool "vmlinux.bin" - depends on BR2_mips || BR2_mipsel || BR2_sh || BR2_sh64 + depends on BR2_mips || BR2_mipsel || BR2_sh config BR2_LINUX_KERNEL_VMLINUX bool "vmlinux"
package/gdb/Config.in +2 -2
@@ -40,10 +40,10 @@ config BR2_PACKAGE_GDB_DEBUGGER bool "full debugger" select BR2_PACKAGE_NCURSES depends on BR2_USE_WCHAR - depends on !BR2_sh && !BR2_sh64 && !BR2_microblaze && !BR2_bfin + depends on !BR2_sh && !BR2_microblaze && !BR2_bfin comment "full gdb on target needs a toolchain w/ wchar" - depends on !BR2_sh && !BR2_sh64 && !BR2_microblaze && !BR2_bfin + depends on !BR2_sh && !BR2_microblaze && !BR2_bfin depends on !BR2_USE_WCHAR if BR2_PACKAGE_GDB_DEBUGGER
package/libunwind/Config.in +2 -2
@@ -3,7 +3,7 @@ config BR2_PACKAGE_LIBUNWIND depends on BR2_TOOLCHAIN_HAS_THREADS depends on (BR2_UCLIBC_VERSION_SNAPSHOT || BR2_TOOLCHAIN_USES_GLIBC) # {g,s}etcontext depends on BR2_arm || BR2_armeb || BR2_mips || BR2_mipsel || BR2_mips64 || \ - BR2_mips64el || BR2_powerpc || BR2_sh || BR2_sh64 || BR2_i386 || BR2_x86_64 + BR2_mips64el || BR2_powerpc || BR2_sh || BR2_i386 || BR2_x86_64 help C API to determine the call-chain of a program.
@@ -11,5 +11,5 @@ config BR2_PACKAGE_LIBUNWIND comment "libunwind needs a uclibc snapshot or (e)glibc toolchain w/ threads" depends on BR2_arm || BR2_armeb || BR2_mips || BR2_mipsel || BR2_mips64 || \ - BR2_mips64el || BR2_powerpc || BR2_sh || BR2_sh64 || BR2_i386 || BR2_x86_64 + BR2_mips64el || BR2_powerpc || BR2_sh || BR2_i386 || BR2_x86_64 depends on !BR2_TOOLCHAIN_HAS_THREADS || !(BR2_UCLIBC_VERSION_SNAPSHOT || BR2_TOOLCHAIN_USES_GLIBC)
toolchain/toolchain-buildroot/Config.in +2 -2
@@ -45,7 +45,7 @@ config BR2_TOOLCHAIN_BUILDROOT_EGLIBC depends on BR2_arm || BR2_armeb || BR2_aarch64 || \ BR2_i386 || BR2_mips || BR2_mipsel || \ BR2_mips64 || BR2_mips64el || BR2_powerpc || \ - BR2_sh || BR2_sh64 || BR2_sparc || \ + BR2_sh || BR2_sparc || \ BR2_x86_64 || BR2_microblaze || BR2_powerpc64 depends on BR2_USE_MMU depends on !BR2_STATIC_LIBS
@@ -64,7 +64,7 @@ config BR2_TOOLCHAIN_BUILDROOT_GLIBC BR2_i386 || BR2_mips || BR2_mipsel || \ BR2_mips64 || BR2_mips64el || BR2_powerpc || \ BR2_powerpc64 || BR2_powerpc64le || BR2_sh || \ - BR2_sh64 || BR2_sparc || BR2_x86_64 || \ + BR2_sparc || BR2_x86_64 || \ BR2_microblaze || BR2_nios2 depends on BR2_USE_MMU depends on !BR2_STATIC_LIBS
Signature · 1 line
1.7.10.4
PATCH 1/1 sh64: drop support for architecture
Dear Waldemar Brodkorb,
Quoted 9 lines · Waldemar Brodkorb
There seems to be no hardware or emulator available for this architecture. Someone from ST Microelectronics told me that sh64/sh5 projects are dropped over ten years ago. I found nothing about real hardware on the sites of Hitachi or Renesas.
We should drop this.
Support in uClibc-ng will be dropped in 1.1.Signed-off-by Waldemar Brodkorb <[email protected]>
Maybe we should start by marking it deprecated for this release cycle? Or broken?
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/1 sh64: drop support for architecture
Hi Thomas,
Thomas Petazzoni wrote,
Quoted 11 lines
Dear Waldemar Brodkorb,
Quoted 8 lines · Waldemar Brodkorb
There seems to be no hardware or emulator available for this architecture. Someone from ST Microelectronics told me that sh64/sh5 projects are dropped over ten years ago. I found nothing about real hardware on the sites of Hitachi or Renesas.
We should drop this.
Support in uClibc-ng will be dropped in 1.1.
Quoted 3 lines
Quoted 1 line
Signed-off-by Waldemar Brodkorb <[email protected]>Maybe we should start by marking it deprecated for this release cycle?
You normally do this. But do you have _any_ user using this in buildroot? I thought the deprecation procedure is for features/architecturs or whatever, which might have an existing userbase.
But maybe someone knows of any device/emulator.
best regards
Waldemar
PATCH 1/1 sh64: drop support for architecture
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Waldemar" == Waldemar Brodkorb <[email protected]> writes:
Hi,
Quoted 7 lines
Quoted 1 line
Maybe we should start by marking it deprecated for this release cycle?
You normally do this. But do you have _any_ user using this in buildroot? I thought the deprecation procedure is for features/architecturs or whatever, which might have an existing userbase.
But maybe someone knows of any device/emulator.
I'm not aware of any users or emulator, but a limited deprecation time would atleast give people a chance to speak up.
Signature · 1 line
Bye, Peter Korsgaard
PATCH 1/1 sh64: drop support for architecture
In reply to Waldemar BrodkorbDear Waldemar Brodkorb,
Quoted 9 lines · Waldemar Brodkorb
There seems to be no hardware or emulator available for this architecture. Someone from ST Microelectronics told me that sh64/sh5 projects are dropped over ten years ago. I found nothing about real hardware on the sites of Hitachi or Renesas.
We should drop this.
Support in uClibc-ng will be dropped in 1.1.Signed-off-by Waldemar Brodkorb <[email protected]>
Following my and Peter comments, we'd prefer to see this feature to be marked as deprecated. I've marked the patch as "Rejected" in patchwork. Can you cook a patch simply marking sh64 as deprecated?
Thanks a lot!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/1 sh64: drop support for architecture
Hi Thomas,
Thomas Petazzoni wrote,
Quoted 11 lines
Dear Waldemar Brodkorb,
Quoted 8 lines · Waldemar Brodkorb
There seems to be no hardware or emulator available for this architecture. Someone from ST Microelectronics told me that sh64/sh5 projects are dropped over ten years ago. I found nothing about real hardware on the sites of Hitachi or Renesas.
We should drop this.
Support in uClibc-ng will be dropped in 1.1.
Quoted 5 lines
Quoted 1 line
Signed-off-by Waldemar Brodkorb <[email protected]>Following my and Peter comments, we'd prefer to see this feature to be marked as deprecated. I've marked the patch as "Rejected" in patchwork. Can you cook a patch simply marking sh64 as deprecated?
Is there documentation how to do this?
best regards
Waldemar
PATCH 1/1 sh64: drop support for architecture
Quoted 14 lines · Waldemar Brodkorb
Hi Thomas,
Thomas Petazzoni wrote,Quoted 11 lines
Dear Waldemar Brodkorb,
Quoted 8 lines · Waldemar Brodkorb
There seems to be no hardware or emulator available for this architecture. Someone from ST Microelectronics told me that sh64/sh5 projects are dropped over ten years ago. I found nothing about real hardware on the sites of Hitachi or Renesas.
We should drop this.
Support in uClibc-ng will be dropped in 1.1.
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Signed-off-by Waldemar Brodkorb <[email protected]>Following my and Peter comments, we'd prefer to see this feature to be marked as deprecated. I've marked the patch as "Rejected" in patchwork. Can you cook a patch simply marking sh64 as deprecated?
Is there documentation how to do this?
Just add
depends on BR2_DEPRECATED_SINCE_2015_05
(check 'git log -p --grep deprecate' for examples)
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F