Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] arch: remove support for SuperH 2 and SuperH 3
Date: Tue, 09 Apr 2013 08:14:53 +0200	[thread overview]
Message-ID: <5163B1DD.3030401@mind.be> (raw)
In-Reply-To: <1365362725-30251-3-git-send-email-thomas.petazzoni@free-electrons.com>

On 07/04/13 21:25, Thomas Petazzoni wrote:
> The SuperH 2 architecture is a noMMU architecture from Renesas, and
> its Linux support is really poor. A number of packages fail to build,
> the kernel support is almost inexistant, we have never heard of any
> user of it.
>
> I was originally the one who introduced support for SuperH 2, but the
> project switched to a different architecture due to the poor Linux
> support for SuperH 2.
>
> Regarding SuperH 3, I've never heard of Linux support for it that is
> used in practice.
>
> Signed-off-by: Thomas Petazzoni<thomas.petazzoni@free-electrons.com>
> ---
>   arch/Config.in.sh                        |   18 ++------------
>   package/flashbench/flashbench.mk         |    4 +--
>   package/kexec/Config.in                  |    2 +-
>   package/multimedia/mplayer/Config.in     |    3 +--
>   toolchain/toolchain-external/Config.in   |   40 ------------------------------
>   toolchain/toolchain-external/ext-tool.mk |    6 -----
>   toolchain/uClibc/uclibc.mk               |   20 ---------------
>   7 files changed, 6 insertions(+), 87 deletions(-)

  git grep 'sh[23]' tells me:

- some comments in qemu.mk can be removed;
- package/binutils/binutils-*/120-sh-conf.patch can probably be removed 
(I think the target name is always sh-x-y for sh4).

  Regards,
  Arnout

-- 
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

  reply	other threads:[~2013-04-09  6:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-07 19:25 [Buildroot] [PATCH 0/2] Remove SH2 and SH3 support Thomas Petazzoni
2013-04-07 19:25 ` [Buildroot] [PATCH 1/2] fs/jffs2: refactor endianess selection to use BR2_ENDIAN Thomas Petazzoni
2013-04-11 13:57   ` Peter Korsgaard
2013-04-07 19:25 ` [Buildroot] [PATCH 2/2] arch: remove support for SuperH 2 and SuperH 3 Thomas Petazzoni
2013-04-09  6:14   ` Arnout Vandecappelle [this message]
2013-04-11  9:04   ` phil.edworthy at renesas.com
2013-04-11  9:50     ` Thomas Petazzoni
2013-04-11 10:11       ` phil.edworthy at renesas.com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5163B1DD.3030401@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox