On Tue, Feb 21, 2017 at 9:14 AM, Alexandre Belloni <alexandre.belloni@xxxxxxxxxxxxxxxxxx> wrote: > On 21/02/2017 at 18:43:35 +0200, Andy Shevchenko wrote: >> >> Come on, v4.10 has just been release and >> >> It doesn't build anymore. And current case even worse >> Face it. It's dead. >> > > I agree it hasn't seen any significant development in a while but I'm > not the on able to take that decision. I've been wanting to add devicetree support for some time, but I no longer remember how to build the toolchain, and I don't have fond memories of that whole process. And the fact that 4.2.4-atmel.1.1.3.avr32linux.1 is still the most current version of gcc doesn't make me very optimistic. So while Hans-Christian and others have been doing a great job of keeping AVR32 on life support, I tend to think that if there's not enough enthusiasm for the architecture to build a modern toolchain or add support for device tree, avr32-linux probably isn't going anywhere exciting. > A few weeks ago, I was telling Boris to let it not build for a while and > then remove it. You already went out of your way to make it work. Again, > feel free to send a patch removing avr32. I can only see a lot of > benefits for the Atmel ARM SoCs and the many cleanups that will follow. Agree, I can't help but feel that the AVR32 support is doing more harm than good at this point. > If nobody complains about the 4.10 breakage, You'll have plenty of time > to remove it for 4.12 I'm fine with that, but I haven't put much effort into keeping it alive lately. If Hans-Christian agrees, I'm willing to post a patch to remove it, or ack someone else's patch. Håvard -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
