Received: by 10.180.103.197 with SMTP id fy5mr1722128wib.1.1344340579449; Tue, 07 Aug 2012 04:56:19 -0700 (PDT) Path: n2ni9357338win.0!nntp.google.com!goblin3!goblin1!goblin.stu.neva.ru!uio.no!nntp.uio.no!.POSTED!not-for-mail From: Max Filippov Newsgroups: fa.linux.kernel Subject: Re: xtensa port maintenance Date: Tue, 07 Aug 2012 11:56:19 UTC Organization: Internet mailing list Lines: 37 Sender: linux-kernel-ow...@vger.kernel.org Message-ID: References: NNTP-Posting-Host: mail-jess.uio.no Mime-Version: 1.0 X-Trace: readme.uio.no 1344340579 15246 129.240.7.9 (7 Aug 2012 11:56:19 GMT) X-Complaints-To: abuse@uio.no NNTP-Posting-Date: Tue, 7 Aug 2012 11:56:19 +0000 (UTC) Cc: Chris Zankel , linux-ker...@vger.kernel.org, linux-xte...@linux-xtensa.org, linux-n...@vger.kernel.org, Linus Torvalds , Andrew Morton , Greg KH , Stephen Rothwell , Marc Gauthier , Kirill Krinkin To: Geert Uytterhoeven DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=eydl1jZG2VhIQYEuRFAvCS7lQMun6/6OHJejbz0ENdI=; b=08D4kbJL2STs3dPq2bRTmDdgF/KMvy/m5mZ+dnbYcM/D60sAkGBthl/EiOPMYf72ZN 5jfm4HwuapMlmClbTNAOmLF+eMUFymaOm4BzYUs28sGCGq08IqmLTORTq//e1da1W0bv orRV5FVW61xBF6wfM8xh5bDHQgG/A5F149my3AWoftq3y1ozG4PUizievobBSc01FKYx VpP4cZZ55Md4YCQ794bsV3Yf2IfaKuExRrCTRTqu1DaO9rzc7ejmzx9tREv/8KpOfP8R 6fbjb/3kbQuKpMyFUpWo+apwBwNTlUtQBDxYAvG8VJLjCa8/iFe/ll3O+aSbjaxrZgab E0gw== In-Reply-To: List-ID: X-Mailing-List: linux-ker...@vger.kernel.org Original-Date: Tue, 7 Aug 2012 15:56:11 +0400 Original-Message-Id: Original-References: <50205592.1030...@gmail.com> <5020AA5B.4080...@zankel.net> Content-Type: text/plain; charset=ISO-8859-1 On Tue, Aug 7, 2012 at 3:36 PM, Geert Uytterhoeven wrote: > Hi Chris, > > 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. -- Max -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/