From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Anyone interested in the AVR32 architecture?
Date: Sun, 6 Apr 2014 15:33:22 +0200 [thread overview]
Message-ID: <20140406153322.3c71b9ad@skate> (raw)
Hello,
Almost two months ago, Simon Dawson, said he would no longer have the
possibility of maintaining the AVR32 support in Buildroot, and was
asking whether someone could step up to continue maintaining this
architecture. Two months later, there has been no volunteer to do that.
The AVR32 architecture is problematic, because it is been abandoned by
Atmel, there is no upstream support in many of the toolchain components
(binutils, gcc, etc.), the uClibc support only works with the old
uClibc 0.9.31, a number of packages are having issues on AVR32 due to
these problems.
Therefore, unless someone steps up to maintain the AVR32 architecture
moving forward, I'm proposing to mark this architecture as deprecated
for the 2014.05 release. It will not be removed at this point, but it
will no longer be visible by default from menuconfig, and we will stop
doing autobuilder testing for this architecture.
So to sum up: if you're interested in AVR32, please speak up, now!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
reply other threads:[~2014-04-06 13:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140406153322.3c71b9ad@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