From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] toolchain/arm: drop generic and old, add fa526/626, unify strongarm
Date: Sun, 7 Apr 2013 22:01:11 +0200 [thread overview]
Message-ID: <20130407220111.2e9b5b7e@skate> (raw)
In-Reply-To: <1365096588-1932-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Thu, 4 Apr 2013 14:29:45 -0300, Gustavo Zacarias wrote:
> * Add Faraday FA526/626 as suggested on bug #1291
> Note however that these cores are v4 and NOT v4t.
>
> * Make the sa110 & sa1110 cores -> strongarm since they're the same.
>
> * Drop all of the ARM variants lower than v4 including generic,
> there's no point in supporting obsolete targets.
>
> * Fix uClibc USE_BX logic, it was always on, this would break the new
> FA526/626 support and broke StrongARM since it's a v4 core.
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
For the four patches:
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
--
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:[~2013-04-07 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 17:29 [Buildroot] [PATCH 1/4] toolchain/arm: drop generic and old, add fa526/626, unify strongarm Gustavo Zacarias
2013-04-04 17:29 ` [Buildroot] [PATCH 2/4] openssl: adjust ARM optimizations Gustavo Zacarias
2013-04-04 17:29 ` [Buildroot] [PATCH 3/4] speex: " Gustavo Zacarias
2013-04-04 17:29 ` [Buildroot] [PATCH 4/4] ffmpeg: " Gustavo Zacarias
2013-04-07 20:01 ` Thomas Petazzoni [this message]
2013-04-11 7:30 ` [Buildroot] [PATCH 1/4] toolchain/arm: drop generic and old, add fa526/626, unify strongarm Peter Korsgaard
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=20130407220111.2e9b5b7e@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