On Tue, Aug 7, 2012 at 3:36 PM, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > Hi Chris, > > On Tue, Aug 7, 2012 at 7:40 AM, Chris Zankel <chris@xxxxxxxxxx> 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-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
