From: Duane Ellis <duane-gcc-help@duaneellis.com>
To: gcc-help@gcc.gnu.org, rem@riscnx.net
Subject: Re: ARM Configure Targets
Date: Thu, 06 Dec 2007 01:18:00 -0000 [thread overview]
Message-ID: <47574DD1.9000808@duaneellis.com> (raw)
Remy> Where can I find further information on specific [ARM] targets?
You should learn about the "cross-gcc" mailing list.
See this site for the archive: http://sourceware.org/ml/crossgcc/
What is the _exact_ target (chip) you want?
ie: A full arm-soc solution (like Xscale)
or: A tiny arm7tdmi micro-controller type, with only 32K flash on chip?
What is the _exact_ OS the board will run?
ie: Roll your own
or: Linux, great for Xscale, won't run on tiny micro-controllers.
or: Some commercial thing, there are many.
or: Something totally weirdo..
Depending upon your answer, I might have something that will help you.
-Duane.
next reply other threads:[~2007-12-06 1:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 1:18 Duane Ellis [this message]
2007-12-06 4:47 ` Remy Fenn
-- strict thread matches above, loose matches on Subject: below --
2007-12-05 13:20 Remy Fenn
2007-12-05 15:21 ` Ian Lance Taylor
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=47574DD1.9000808@duaneellis.com \
--to=duane-gcc-help@duaneellis.com \
--cc=gcc-help@gcc.gnu.org \
--cc=rem@riscnx.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).