kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: dhylands@gmail.com (Dave Hylands)
To: kernelnewbies@lists.kernelnewbies.org
Subject: ARM Cross Compilation Toolchain on x86 machine
Date: Fri, 7 Jan 2011 08:26:13 -0800	[thread overview]
Message-ID: <AANLkTimH=uwOciKYUu9R8je1z4z3L6G_T0oyC5kTL969@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin+vx=8COLYP8LSqcnQ3H1CWsM27DegTsio6BKC@mail.gmail.com>

Hi Madhavi,

On Fri, Jan 7, 2011 at 1:30 AM, Madhavi Manchala
<madhavi.linux@gmail.com> wrote:
...snip...
> Where can I get the list of supported CPU family types for ARM
> architecture like ARM5, ARM7, ARM926EJ etc. In case of Power
> Architecture (PPC) there is a list as shown in the below link at ELDK
> site
> http://www.denx.de/wiki/view/DULG/ELDKSupportedTargetArchitectures
>
> The same is also mentioned in the table at 3.6.A Table of possible
> values for $CROSS_COMPILE section of the ELDK at
> http://www.denx.de/wiki/view/DULG/ELDKUsage
>
> For us, ARM9 is suitable.

You can try using

arm-xxx-gcc --target-help

(replace xxx appropriately). This should list the targets which are
supported by that particular compiler. For example, when I use my
gumstix cross compiler, I get the following output:

  Known ARM CPUs (for use with the -mcpu= and -mtune= options):
    cortex-m3, cortex-r4, cortex-a8, arm1156t2-s, mpcore, mpcorenovfp,
    arm1176jzf-s, arm1176jz-s, arm1136jf-s, arm1136j-s, arm1026ej-s, arm926ej-s,
    iwmmxt, xscale, arm1022e, arm1020e, arm10e, arm968e-s, arm966e-s, arm946e-s,
    arm9e, arm1020t, arm10tdmi, ep9312, arm940t, arm922t, arm920t, arm920,
    arm9tdmi, arm9, arm740t, arm720t, arm710t, arm7tdmi-s, arm7tdmi,
    strongarm1110, strongarm1100, strongarm110, strongarm, arm810, arm8,
    arm7dmi, arm7dm, arm7m, arm7500fe, arm7500, arm7100, arm710c, arm720,
    arm710, arm700i, arm700, arm70, arm7di, arm7d, arm7, arm620, arm610, arm600,
    arm60, arm6, arm3, arm250, arm2

  Known ARM architectures (for use with the -march= option):
    iwmmxt, ep9312, armv7-m, armv7-r, armv7-a, armv7, armv6t2, armv6zk, armv6z,
    armv6k, armv6j, armv6, armv5te, armv5e, armv5t, armv5, armv4t, armv4,
    armv3m, armv3, armv2a, armv2

Dave Hylands

  reply	other threads:[~2011-01-07 16:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 15:38 ARM Cross Compilation Toolchain on x86 machine Madhavi Manchala
2011-01-06 15:48 ` vinit agrawal
2011-01-07  0:55   ` Alexandre Courbot
2011-01-07  7:34   ` Madhavi Manchala
2011-01-07  8:36     ` Alexandre Courbot
2011-01-07  1:14 ` Manohar Vanga
2011-01-07  9:30   ` Madhavi Manchala
2011-01-07 16:26     ` Dave Hylands [this message]
2011-02-01 16:34       ` Chaitannya Mahatme
2011-02-01 17:53         ` vinit agrawal

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='AANLkTimH=uwOciKYUu9R8je1z4z3L6G_T0oyC5kTL969@mail.gmail.com' \
    --to=dhylands@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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;
as well as URLs for NNTP newsgroup(s).