lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170327152604.1d00cd9a@bbrezillon>
Date:   Mon, 27 Mar 2017 15:26:04 +0200
From:   Boris Brezillon <boris.brezillon@...e-electrons.com>
To:     Hans-Christian Noren Egtvedt <egtvedt@...fundet.no>
Cc:     linux-kernel@...r.kernel.org,
        Haavard Skinnemoen <hskinnemoen@...il.com>,
        Nicolas Ferre <nicolas.ferre@...el.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [RFC] remove support for AVR32 architecture

Hi Hans,

On Wed, 1 Mar 2017 21:44:26 +0100
Hans-Christian Noren Egtvedt <egtvedt@...fundet.no> wrote:

> Hello all,
> 
> 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?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ