From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] arch: remove BR2_arm10t
Date: Mon, 15 Sep 2014 23:13:55 +0200 [thread overview]
Message-ID: <20140915211355.GB3878@free.fr> (raw)
In-Reply-To: <1410814919-11523-3-git-send-email-thomas.petazzoni@free-electrons.com>
Thomas, All,
On 2014-09-15 23:01 +0200, Thomas Petazzoni spake thusly:
> The BR2_arm10t option is not correct as it references an ARM family,
> while other options indicate a specific ARM core. The ARM cores in
> ARM10 family are ARM1020E, ARM1022E and ARM1026EJ-S according to
> Wikipedia. However, those are clearly very rare, and Wikipedia also
> indicates two Conexant ADSL-related SoC as being part of this family
> of ARM cores. Therefore, this commit removes this ARM family.
You forgot the reference to BR2_arm10t we have in nettle.mk
Regards,
Yann E. MORIN.
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> arch/Config.in.arm | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/arch/Config.in.arm b/arch/Config.in.arm
> index 5ae2378..201ff1d 100644
> --- a/arch/Config.in.arm
> +++ b/arch/Config.in.arm
> @@ -54,9 +54,6 @@ config BR2_arm926t
> bool "arm926t"
> select BR2_ARM_CPU_MAYBE_HAS_VFPV2
> select BR2_ARM_CPU_HAS_THUMB
> -config BR2_arm10t
> - bool "arm10t"
> - select BR2_ARM_CPU_HAS_THUMB
> config BR2_arm1136jf_s_r0
> bool "arm1136jf_s rev0"
> select BR2_ARM_CPU_HAS_VFPV2
> @@ -367,7 +364,6 @@ config BR2_GCC_TARGET_ARCH
> default "armv4t" if BR2_arm920t
> default "armv4t" if BR2_arm922t
> default "armv5te" if BR2_arm926t
> - default "armv5t" if BR2_arm10t
> default "armv6j" if BR2_arm1136jf_s_r0
> default "armv6k" if BR2_arm1136jf_s_r1
> default "armv6zk" if BR2_arm1176jz_s
> --
> 2.0.0
>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-09-15 21:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 21:01 [Buildroot] [PATCH 0/4] Fix march/mcpu conflict on ARM Thomas Petazzoni
2014-09-15 21:01 ` [Buildroot] [PATCH 1/4] arch: remove BR2_arm920 reference Thomas Petazzoni
2014-09-15 21:08 ` Yann E. MORIN
2014-09-18 20:12 ` Peter Korsgaard
2014-09-15 21:01 ` [Buildroot] [PATCH 2/4] arch: remove BR2_arm10t Thomas Petazzoni
2014-09-15 21:13 ` Yann E. MORIN [this message]
2014-09-15 21:16 ` Thomas Petazzoni
2014-09-18 20:12 ` Peter Korsgaard
2014-09-15 21:01 ` [Buildroot] [PATCH 3/4] arch: do not distinguish revisions of ARM1136JF-S Thomas Petazzoni
2014-09-15 21:16 ` Benoît Thébaudeau
2014-09-15 21:33 ` Yann E. MORIN
2014-09-15 21:39 ` Thomas Petazzoni
2014-09-15 21:44 ` Benoît Thébaudeau
2014-09-15 21:50 ` Thomas Petazzoni
2014-09-15 22:36 ` Benoît Thébaudeau
2014-09-15 22:02 ` Yann E. MORIN
2014-09-15 22:37 ` Benoît Thébaudeau
2014-09-15 21:48 ` Yann E. MORIN
2014-09-15 21:01 ` [Buildroot] [PATCH 4/4] arch: remove BR2_GCC_TARGET_ARCH definitions on ARM Thomas Petazzoni
2014-09-15 22:09 ` Yann E. MORIN
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=20140915211355.GB3878@free.fr \
--to=yann.morin.1998@free.fr \
--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