From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: FA526 / CNS2132 / TS-7500 build configuration
Date: Sun, 19 Sep 2010 21:39:11 -0700 [thread overview]
Message-ID: <20100920043911.GA7809@gmail.com> (raw)
In-Reply-To: <AANLkTinKOg2beadzpOyLQ+eQtQa4KH5KG11OyF_jCC64@mail.gmail.com>
On (19/09/10 19:18), R.T. McGee wrote:
> The Faraday FA526 core is used in ARM processors like the Semi STR8132
> / Cavium CNS2132 which is in my Technologic Systems TS-7500 board in
> addition to some NAS boxes out there. From what I have read, it
> basically resembles a ARM920T but has NO thumb interworking support
> which makes it not fully EABI compliant (
> http://www.mail-archive.com/openocd-development@lists.berlios.de/msg05856.html
> ). I have build a few tool chains manually that produce working code
> using a configuration meant for a OABI style armv4 which makes sense
> since it uses NO thumb instructions, but I am not sure this is
> optimal.
eabi is now supported on armv4 architecture and we have OE internal
toolchain also support it from gcc 4.4.x onwards.
>
> What is the best way to move forward to setup a OpenEmbedded
> distro/machine configuration for something like the TS-7500 or a
> general FA526 configuration?
look at any armv4 machines we have in OE e.g. collie and distros like
minimal or angstrom
DISTRO=minimal MACHINE=collie bitbake minimal-image
I guess, one option is setup OABI ARMv4
> style setup but this was removed from things like angstrom a while
> ago. Switching to OABI just to get rid of thumb seems a little silly.
>
> It would be nice to figure out a way to use EABI ARMv4T toolkit but
> pass flags like -mapcs-32 -mno-thumb-interwork (just a guess) to GCC
> to insure no thumb instructions (other weird things are discussed in
> http://wiki.debian.org/ArmEabiPort#Otherscenarios ). The linker
> option -fix-v4bx looks promising for the linker also. A lot of things
> are possible solutions, but whats the cleanest way to work it into
> OpenEmbedded's build system?
its already functional in OE.
>
> Any suggestion would be helpful. Thanks.
>
Thx
-Khem
next prev parent reply other threads:[~2010-09-20 4:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinFs+k=b-UowmKXY9kWFvSdv772K1n7B+uzkJHL@mail.gmail.com>
2010-09-19 23:18 ` FA526 / CNS2132 / TS-7500 build configuration R.T. McGee
2010-09-20 4:39 ` Khem Raj [this message]
[not found] ` <AANLkTinpUwuVykASgF2gj=3QRTmGpa5mZpS6_TwrLpGj@mail.gmail.com>
[not found] ` <AANLkTinbNucPm-bK52mrOhjOo9mJfWHUBkBct6KXCXsm@mail.gmail.com>
2010-10-10 1:02 ` R.T. McGee
2010-10-10 5:32 ` Petr Štetiar
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=20100920043911.GA7809@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.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