<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On Friday 07 January 2011 09:56 PM, Dave Hylands wrote:
<blockquote
cite="mid:AANLkTimH=uwOciKYUu9R8je1z4z3L6G_T0oyC5kTL969@mail.gmail.com"
type="cite">
<pre wrap="">Hi Madhavi,
On Fri, Jan 7, 2011 at 1:30 AM, Madhavi Manchala
<a class="moz-txt-link-rfc2396E" href="mailto:madhavi.linux@gmail.com"><madhavi.linux@gmail.com></a> wrote:
...snip...
</pre>
<blockquote type="cite">
<pre wrap="">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
<a class="moz-txt-link-freetext" href="http://www.denx.de/wiki/view/DULG/ELDKSupportedTargetArchitectures">http://www.denx.de/wiki/view/DULG/ELDKSupportedTargetArchitectures</a>
The same is also mentioned in the table at 3.6.A Table of possible
values for $CROSS_COMPILE section of the ELDK at
<a class="moz-txt-link-freetext" href="http://www.denx.de/wiki/view/DULG/ELDKUsage">http://www.denx.de/wiki/view/DULG/ELDKUsage</a>
For us, ARM9 is suitable.
</pre>
</blockquote>
<pre wrap="">
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
_______________________________________________
Kernelnewbies mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a>
<a class="moz-txt-link-freetext" href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a>
</pre>
</blockquote>
Hi Madhavi,<br>
<br>
<br>
Read this article
<a class="moz-txt-link-freetext" href="http://wiki.embeddednirvana.org/Building_your_own_toolchain">http://wiki.embeddednirvana.org/Building_your_own_toolchain</a>. A brief
given a brief about explanation on instruction set and cross compile
target is given. <br>
It is highly recommended that you use the toolchain supplied from the
chip manufacturer since it would be optimised for the chip you are
using. A program compiled for ARM7 can run perfectly well on arm11
arch, but then you won't be able to utilize h/w features of the arm11
arch. <br>
<br>
As for the complete list, it's available on gcc's site
<a class="moz-txt-link-freetext" href="http://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html">http://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html</a> <br>
<div class="moz-signature">-- <br>
Cheers !!!<br>
Chaitannya<br>
<br>
follow me on twitter <a h="ref=3D"http://twitter.com/chaitannya"">http://twitter.com/chaitannya</a>
<br>
<br>
I believe there's a hero in all of us <br>
who keeps us honest, gives us strength, makes us noble, and finally
allows us to die with pride,<br>
even though sometimes we have to be steady, and give up the thing we
want the most... even our dreams.<br>
- Spider Man 2<br>
</div>
</body>
</html>