From: Chris Zankel <chris@zankel.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] add support for xtensa back to buildroot
Date: Wed, 07 Nov 2012 19:38:14 -0800 [thread overview]
Message-ID: <509b2928.67dc440a.70c6.6325@mx.google.com> (raw)
Hi,
It would be great if you could add support for Xtensa back to buildroot.
I understand that it was removed because it required a lot of additional
files and special handling, which became obsolete and hard to maintain
over time.
These two patches are much more aligned with other architectures with only
very minimal overhead. I also just recently updated uClibc and can build
buildroot out of the box, so we can now better support and maintain it.
Thanks,
-Chris
----------------------------------------------------------------
Chris Zankel (2):
xtensa: add support for the Xtensa architecture
xtensa: support configurable processor configurations
arch/Config.in | 8 ++++++++
arch/Config.in.common | 1 +
arch/Config.in.xtensa | 30 ++++++++++++++++++++++++++++++
linux/Config.in | 3 ++-
package/autoconf/Config.in | 6 ++++--
package/automake/Config.in | 6 ++++--
package/binutils/binutils.mk | 9 +++++++++
package/ltrace/Config.in | 1 +
package/perl/Config.in | 4 +++-
toolchain/gcc/gcc-uclibc-4.x.mk | 4 ++++
toolchain/gdb/gdb.mk | 4 ++++
toolchain/toolchain-common.in | 2 +-
toolchain/uClibc/uclibc.mk | 1 +
13 files changed, 72 insertions(+), 7 deletions(-)
create mode 100644 arch/Config.in.xtensa
next reply other threads:[~2012-11-08 3:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 3:38 Chris Zankel [this message]
2012-11-08 7:22 ` [Buildroot] [PATCH 0/2] add support for xtensa back to buildroot Thomas Petazzoni
2012-11-09 4:49 ` Chris Zankel
2012-11-09 8:14 ` Thomas Petazzoni
2012-11-10 10:57 ` Thomas Petazzoni
2012-11-12 20:23 ` Chris Zankel
2012-11-12 21:01 ` Thomas Petazzoni
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=509b2928.67dc440a.70c6.6325@mx.google.com \
--to=chris@zankel.net \
--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