From: Adrian Bunk <bunk@stusta.de>
To: spyro@f2s.com, john@dnsworld.co.uk
Cc: linux-kernel@vger.kernel.org, rmk@arm.linux.org.uk
Subject: RFC: Remove the arm26 port
Date: Sun, 29 Jul 2007 13:50:40 +0200 [thread overview]
Message-ID: <20070729115040.GD30976@stusta.de> (raw)
In-Reply-To: <20070707201208.GJ3492@stusta.de>
Considering the state of the arm26 port, I do hereby suggest to remove
it from the Linx kernel since it's far from a usable state and doesn't
seem to come back into a usable state.
If anyone wants to work on getting this port back into a usable state in
the forseeable future he should speak up now.
cu
Adrian
On Sat, Jul 07, 2007 at 10:12:08PM +0200, Adrian Bunk wrote:
> I'm wondering what the status of the arm26 port in the kernel is:
>
> AFAIR gcc support for this architecture was deprecated in gcc 3.4 and
> removed in gcc 4.0. This implies that either someone will have to re-add
> support to gcc in the next 1-2 years or the kernel port will become
> useless with the next increase of the minimum gcc requirement for the
> kernel.
>
> The other point is that I tried to cross-compile an arm26 defconfig.
> I gave up after running into several compile errors, and it doesn't seem
> as if any recent kernel could be compiled.
>
> Is the arm26 kernel port already unused dead code or is some work for
> getting it back into shape pending?
>
> cu
> Adrian
next prev parent reply other threads:[~2007-07-29 11:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 20:12 Status of the arm26 port? Adrian Bunk
2007-07-29 11:50 ` Adrian Bunk [this message]
2007-07-29 12:10 ` RFC: Remove the arm26 port Christoph Hellwig
2007-07-29 12:31 ` Russell King
2007-07-29 13:05 ` Dr. David Alan Gilbert
2007-07-29 22:58 ` ian
2007-07-30 11:49 ` [2.6 patch] " Adrian Bunk
2007-07-30 22:08 ` Satyam Sharma
2007-07-31 1:25 ` Andrew Morton
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=20070729115040.GD30976@stusta.de \
--to=bunk@stusta.de \
--cc=john@dnsworld.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=spyro@f2s.com \
/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