Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755130Ab2HGOfg (ORCPT ); Tue, 7 Aug 2012 10:35:36 -0400 Received: from mail-vc0-f174.google.com ([209.85.220.174]:53436 "EHLO mail-vc0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752518Ab2HGOfH (ORCPT ); Tue, 7 Aug 2012 10:35:07 -0400 MIME-Version: 1.0 In-Reply-To: References: <50205592.1030205@gmail.com> <5020AA5B.4080407@zankel.net> Date: Tue, 7 Aug 2012 16:35:05 +0200 X-Google-Sender-Auth: eSi1lNqwRq2NqyIA6P_ATKNRxsU Message-ID: Subject: Re: xtensa port maintenance From: Geert Uytterhoeven To: Max Filippov Cc: Chris Zankel , linux-kernel@vger.kernel.org, linux-xtensa@linux-xtensa.org, linux-next@vger.kernel.org, Linus Torvalds , Andrew Morton , Greg KH , Stephen Rothwell , Marc Gauthier , Kirill Krinkin Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2211 Lines: 49 Hi Max, On Tue, Aug 7, 2012 at 1:56 PM, Max Filippov wrote: > On Tue, Aug 7, 2012 at 3:36 PM, Geert Uytterhoeven wrote: >> On Tue, Aug 7, 2012 at 7:40 AM, Chris Zankel wrote: >>> On 08/06/2012 04:38 PM, Max Filippov wrote: >>>> AFAIK xtensa linux port is currently in bad shape: it doesn't work in the >>>> mainline, it fails to build in the linux-next. The latest working kernels >>>> for >>>> xtensa are 2.6.29...31 trees hosted at the git.linux-xtensa.org. >>> >>> I wouldn't say it's in bad shape, I just built an vmlinux image from the >>> latest tree (3.6.0-rc1), but it might not be very stable. One of the major >>> issues is not really the kernel but there's actually no way to build a >>> fairly recent version of the toolchain. I have been using a somewhat more >>> recent buildroot version than what is on xtensa-linux.org, but even that >>> version of buildroot is rather old now and needed a few patches. >> >> Are the errors >> >> | dangerous relocation: l32r: literal placed after use: .literal.unlikely >> (http://kisskb.ellerman.id.au/kisskb/buildresult/6845615/) >> >> preventing linking of vmlinux toolchain issues? > > They may be considered as such (toolchain now adds *.unlikely sections which > was not the case previously), or may not, depending on what one would expect > from the toolchain. I have a fix for that issue: > https://github.com/jcmvbkbc/linux-xtensa/commit/edd7c14132388d5c09c57cf12c76c6631a1e0277 Thanks, that indeed fixes the link issue for me! BTW, how do you export a "commitdiff" from the github web interface? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/