From: Chris Zankel <chris@zankel.net>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-xtensa@linux-xtensa.org,
linux-next@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg KH <greg@kroah.com>, Stephen Rothwell <sfr@canb.auug.org.au>,
Marc Gauthier <marc@tensilica.com>,
Kirill Krinkin <kirill.krinkin@gmail.com>
Subject: Re: xtensa port maintenance
Date: Wed, 08 Aug 2012 01:23:58 -0700 [thread overview]
Message-ID: <5022221E.5020804@zankel.net> (raw)
In-Reply-To: <CAMo8BfLLxBeUC-vg6sAxWLjqPt=fwsQEQgjsqqbjurT3vzo-Pw@mail.gmail.com>
Hi Max,
On 08/07/2012 09:43 AM, Max Filippov wrote:
> On Tue, Aug 7, 2012 at 9:40 AM, Chris Zankel <chris@zankel.net> wrote:
>> Hi Max,
>>
>> 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.
> I've been using userspace built from the buildroot image hosted on
> linux-xtensa.org with gcc-4.4.5 + binutils-2.20.1. I use gcc-4.6.3
> (without libc) + binutils-2.22 to build the kernel. I had an impression that
> mentioned buildroot was able to produce userspace where LTP could
> run successfully for days. So, my initial plan is to use that userspace
> with mainline kernel.
Good plan!
> I have a subset thereof that builds toolchain (without libc) and the kernel.
> Buildroot gave me an impression of not very reproducible environment, perhaps
> I spent too little time on it. So I made an image and I hope that
> pre-built image
> may be used, at least in the beginning. I had to lightly patch U-boot hosted on
> linux-xtensa.org to make it work on LX60/110/200 QEMU models. I guess we
> can start with pre-built image of the bootloader too.
I'm not settled on Buildroot, but I had the best experience with it so
far. OpenEmbedded was a real pain when I used it (it might have improved
a lot since, though). I once even started my own build system, but it
became fairly complicated once I wanted to build a bootable system with
a C library and various packages.
> Ok. I'd like to have even generic patches (my current queue is mostly
> generic) reviewed. Do you prefer to read them on github or on the
> linux-xtensa mailing list?
I looked over them briefly, and only had one or two questions. I'll send
them tomorrow (our time).
Thanks,
-Chris
next prev parent reply other threads:[~2012-08-08 8:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 23:38 xtensa port maintenance Max Filippov
2012-08-07 5:40 ` Chris Zankel
2012-08-07 11:36 ` Geert Uytterhoeven
2012-08-07 11:56 ` Max Filippov
2012-08-07 14:35 ` Geert Uytterhoeven
2012-08-07 15:34 ` Max Filippov
2012-08-07 16:57 ` Geert Uytterhoeven
2012-08-07 16:43 ` Max Filippov
2012-08-08 8:23 ` Chris Zankel [this message]
[not found] ` <CAJH6qSc=Xffk85To2wZ=Ynw41Wb385XEpcT_OGjPV7r=i7M+UQ@mail.gmail.com>
2012-08-08 8:08 ` [Linux-Xtensa] " Chris Zankel
2012-08-10 21:15 ` Arnd Bergmann
2012-08-10 22:39 ` Chris Zankel
[not found] ` <5025975D.9030100@gmail.com>
2012-08-11 4:47 ` Marc Gauthier
2012-08-16 19:38 ` Rakesh Jain
2012-08-17 5:34 ` Pete Delaney
2012-08-20 19:17 ` Rakesh Jain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5022221E.5020804@zankel.net \
--to=chris@zankel.net \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=jcmvbkbc@gmail.com \
--cc=kirill.krinkin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=marc@tensilica.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.