From: Christopher Friedt <chrisfriedt@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] arm11 tool chain
Date: Mon, 27 Jul 2009 17:07:10 +0200 [thread overview]
Message-ID: <3ea34a000907270807lab65f23v8dd5e384b4b36187@mail.gmail.com> (raw)
In-Reply-To: <3dc1583f0906300030x6539d425g528cbd15c0783ef@mail.gmail.com>
Hi Jason,
On Tue, Jun 30, 2009 at 9:30 AM, Sven Rebhan<odinshorse@googlemail.com> wrote:
> I would use
>
> -march=armv6j -mtune=arm1136jf-s
It might be wise to include '-mfpu=vfp' in there too. Having not
worked with >ARMv5 chips, I can't say with any certainty whether
-mtune=arm1136jf-s pulls the vfp in by default, although I would
imagine it would if you don't specify arm-softfloat-... .
How did it crossdev work out for you? Did you end up getting a price
for the development board?
Cheers,
Chris
prev parent reply other threads:[~2009-07-27 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 14:47 [gentoo-embedded] arm11 tool chain Melton, Jason
2009-06-29 18:08 ` wireless
2009-06-30 15:40 ` Melton, Jason
2009-06-30 16:15 ` wireless
2009-06-30 7:30 ` Sven Rebhan
2009-06-30 15:56 ` Melton, Jason
2009-07-27 15:07 ` Christopher Friedt [this message]
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=3ea34a000907270807lab65f23v8dd5e384b4b36187@mail.gmail.com \
--to=chrisfriedt@gmail.com \
--cc=gentoo-embedded@lists.gentoo.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