Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1609833 > unrolled thread
| Started by | Boris Brezillon <boris.brezillon@free-electrons.com> |
|---|---|
| First post | 2017-03-27 15:30 +0200 |
| Last post | 2017-03-27 15:40 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [RFC] remove support for AVR32 architecture Boris Brezillon <boris.brezillon@free-electrons.com> - 2017-03-27 15:30 +0200
Re: [RFC] remove support for AVR32 architecture Hans-Christian Noren Egtvedt <egtvedt@samfundet.no> - 2017-03-27 15:40 +0200
| From | Boris Brezillon <boris.brezillon@free-electrons.com> |
|---|---|
| Date | 2017-03-27 15:30 +0200 |
| Subject | Re: [RFC] remove support for AVR32 architecture |
| Message-ID | <tpCSC-hj-23@gated-at.bofh.it> |
Hi Hans, On Wed, 1 Mar 2017 21:44:26 +0100 Hans-Christian Noren Egtvedt <egtvedt@samfundet.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?
[toc] | [next] | [standalone]
| From | Hans-Christian Noren Egtvedt <egtvedt@samfundet.no> |
|---|---|
| Date | 2017-03-27 15:40 +0200 |
| Message-ID | <tpD2i-kn-33@gated-at.bofh.it> |
| In reply to | #1609833 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web