From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Xtensa support
Date: Wed, 21 Sep 2011 08:52:45 +0200 [thread overview]
Message-ID: <20110921085245.149d3c03@skate> (raw)
In-Reply-To: <522C1DF17AF50042AD8AE87F7887BD3D020C5F4943@exch.hq.tensilica.com>
Hello Marc,
Le Tue, 20 Sep 2011 21:01:35 -0700,
Marc Gauthier <marc@tensilica.com> a ?crit :
> If you're curious, some of it is here, but far from cleaned up!!:
>
> http://git.linux-xtensa.org/cgi-bin/git.cgi?p=buildroot/buildroot-new.git;a=shortlog;h=Xtensa-Patches
Sounds like most of those patches are patches against uClibc, binutils
or gdb. It'd be better to have those patches merged in their respective
upstreams rather than integrating those patches into Buildroot.
> > I am remain concerned by the fact that we carry some special stuff
> > to support Xtensa, but he Xtensa architecture support has never been
> > updated since it was merged in Buildroot. Of course, it is our goal
> > to support configurable architectures such as Xtensa, but the
> > support for those architectures needs to be actively maintained in
> > Buildroot upstream.
>
> Yes. For example, some of the xtensa files under /target/ need to be
> moved and/or refactored. And a defconfig added in /configs/.
> (Hopefully you now take pull requests? easier than patches)
We do take pull requests, but we like when patches are posted on the
mailing list as well. This is easy to do with a combination of git
pull-request + git send-email. I can share my little script to do that
if you're interested.
> > Unfortunately, none of the main Buildroot developers have
> > Xtensa-capable hardware, so it's a bit hard to contribute to this
> > effort.
>
> Do I hear volunteers? :-) We've discussed sending out boards in the
> past, but that turned out to be a bit more sideline effort than hoped.
> Looks like an easier approach is to use an instruction set simulator.
> It can boot Linux, so should be fine. If you're interested I'll be
> very happy to share the details. Helping hands are most appreciated.
Having a working emulator setup would definitely be nice. However, to
get volunteers working on something freely, one needs to put some
incentive on the table. And usually, in the embedded space, this
incentive is a nice hardware platform, that the open-source developer
is so happy to receive that he will be interested in contributing. The
charm of having a real hardware platform is a lot higher than the charm
of the emulator, as is the incentive to contribute things :-)
Of course, regardless of whether boards are made available or not, we
will gladly take patches, review them, comment them, and help you
merging as much as possible of the Xtensa support into the mainline
Buildroot.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-09-21 6:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 16:37 [Buildroot] inittab for Busybox Heyendal, Carl
2011-03-15 17:07 ` Thomas Petazzoni
2011-03-15 17:28 ` Charles Krinke
2011-03-15 18:14 ` Heyendal, Carl
2011-03-15 18:22 ` Thomas Petazzoni
2011-03-15 18:32 ` Heyendal, Carl
2011-03-15 20:05 ` Thomas Petazzoni
2011-03-15 20:10 ` Heyendal, Carl
2011-03-16 16:44 ` [Buildroot] Buildroot in use Steve Calfee
2011-03-16 20:08 ` Heyendal, Carl
2011-03-17 12:14 ` William Wagner
2011-03-17 13:53 ` Heyendal, Carl
2011-03-17 17:17 ` Steve Calfee
2011-03-17 19:42 ` Heyendal, Carl
2011-03-17 21:50 ` Steve Calfee
2011-03-18 16:03 ` Thomas Petazzoni
2011-03-18 16:02 ` Thomas Petazzoni
2011-03-18 16:01 ` Thomas Petazzoni
2011-03-17 20:21 ` Grant Edwards
2011-03-18 15:59 ` [Buildroot] Xtensa support Thomas Petazzoni
2011-03-21 21:18 ` Piet Delaney
2011-09-20 18:35 ` Thomas Petazzoni
2011-09-21 4:01 ` Marc Gauthier
2011-09-21 6:52 ` Thomas Petazzoni [this message]
2011-09-21 8:08 ` Piet Delaney
2011-03-27 19:19 ` [Buildroot] Buildroot in use Michael J. Hammel
2011-03-27 23:58 ` Steve Calfee
2011-03-31 17:13 ` Steve Calfee
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=20110921085245.149d3c03@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox