From: Hans-Christian Noren Egtvedt <egtvedt@samfundet.no>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: linux-kernel@vger.kernel.org,
Haavard Skinnemoen <hskinnemoen@gmail.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC] remove support for AVR32 architecture
Date: Mon, 27 Mar 2017 15:35:56 +0200 [thread overview]
Message-ID: <20170327133556.GA24404@samfundet.no> (raw)
In-Reply-To: <20170327152604.1d00cd9a@bbrezillon>
Around Mon 27 Mar 2017 15:26:04 +0200 or thereabout, Boris Brezillon wrote:
> On Wed, 1 Mar 2017 21:44:26 +0100 Hans-Christian Noren Egtvedt <egtvedt@samfundet.no> wrote:
>> The AVR32 architecture is not keeping up with the development of the kernel,
>> and since it shares so much of the drivers with Atmel ARM SoC, it is starting
>> to hinder these drivers to develop swiftly.
>>
>> Also, all AVR32 AP7 SoC processors are end of lifed from Atmel (now
>> Microchip).
>>
>> Finally, the GCC toolchain is stuck at version 4.2.x, and has not received
>> any patches since the last release from Atmel;
>> 4.2.4-atmel.1.1.3.avr32linux.1. When building kernel v4.10, this toolchain is
>> no longer able to properly link the network stack.
>>
>> Haavard and I have came to the conclusion that we feel keeping AVR32 on life
>> support offers more obstacles for Atmel ARMs, than it gives joy to AVR32
>> users. I also suspect there are very few AVR32 users left today, if anybody
>> at all.
>>
>> I have prepared three patches in my for-linus branch in git tree
>> https://git.kernel.org/cgit/linux/kernel/git/egtvedt/linux-avr32.git
>>
>> Shortlog below, patches not inlined as they are quite large IMHO.
>>
>> I will send a formal pull request to Linus unless anybody objects loudly.
>
> Is this still planned for 4.12?
Yes, I have received no objections, only feedback to bits and pieces in
generic areas that can be removed in addition to my initial patch.
--
mvh
Hans-Christian Noren Egtvedt
next prev parent reply other threads:[~2017-03-27 13:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 20:44 [RFC] remove support for AVR32 architecture Hans-Christian Noren Egtvedt
2017-03-01 21:43 ` Andy Shevchenko
2017-03-01 21:55 ` Boris Brezillon
2017-03-02 15:55 ` Nicolas Ferre
2017-03-06 5:58 ` Håvard Skinnemoen
2017-03-06 19:07 ` Hans-Christian Noren Egtvedt
2017-03-27 13:26 ` Boris Brezillon
2017-03-27 13:35 ` Hans-Christian Noren Egtvedt [this message]
2017-05-02 5:52 ` Hans-Christian Noren Egtvedt
2017-05-02 7:46 ` Andy Shevchenko
2017-05-02 8:12 ` Hans-Christian Noren Egtvedt
2017-05-02 8:33 ` Andy Shevchenko
2017-05-02 11:27 ` Andy Shevchenko
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=20170327133556.GA24404@samfundet.no \
--to=egtvedt@samfundet.no \
--cc=boris.brezillon@free-electrons.com \
--cc=hskinnemoen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--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;
as well as URLs for NNTP newsgroup(s).