From: Waldemar Brodkorb <wbx@openadk.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hans-Christian Noren Egtvedt <egtvedt@samfundet.no>
Subject: objective rules for architecture removal
Date: Thu, 18 May 2017 16:45:57 +0200 [thread overview]
Message-ID: <20170518144557.GU11446@waldemar-brodkorb.de> (raw)
Hi Linus,
are there any objective rules for removal of architecture support from
the Linux kernel tree?
I recognized this week that avr32 support was removed recently.
https://lkml.org/lkml/2017/3/1/694
The major reasons are:
- end-of-life for hardware
- no upstream gcc (very old)
- no users or distribution supporting it
- shared driver code with ARM architecture
AVR32 has a working distribution (https://openadk.org) and some users.
A year ago Mario Haustein from Technical University Chemnitz submitted some
patches to OpenADK for better AVR32 support. They have approx. 100 devices in use.
And I donated a NGW100 board to one of the u-boot maintainers to keep u-boot
support solid.
It is possible to use gcc 4.4.7 with some patches, which was used a long time
in OpenWrt avr32 port:
https://cgit.openadk.org/cgi/cgit/openadk.git/tree/toolchain/gcc/patches/4.4.7
I always loved that Linux kernel does support many architectures and keep supporting
all of them. Any chance to rethink about the removal?
Couldn't be the shared drivers be separated, so that the ARM drivers get there
new improvements? It is a naive assumption from an embedded Linux hacker
trying to keep uClibc and all it's architecture support alive.
(https://uclibc-ng.org)
best regards
Waldemar
next reply other threads:[~2017-05-18 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 14:45 Waldemar Brodkorb [this message]
2017-05-18 18:39 ` Linus Torvalds
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=20170518144557.GU11446@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=egtvedt@samfundet.no \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®