public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: C B <csb_80@hotmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Adding xscale support to my eCos config
Date: Wed, 14 Nov 2007 14:05:00 -0000	[thread overview]
Message-ID: <20071114133044.GX4401@lunn.ch> (raw)
In-Reply-To: <BAY105-W510A7E2AF8236B4AD3C38EA810@phx.gbl>

On Wed, Nov 14, 2007 at 08:19:46AM -0500, C B wrote:
> 
> 

> Coming from a long background developing Applications in Java to the
> embedded world is quite a switch so please bear with me.  I've got
> an eCos configuration working based on the latest from CVS for an
> ARM9 based target from Atmel.  I've written simple applications in
> C, linked against the eCos libs and successfully executed them on my
> target.  So, my question: My target supports an extended DSP
> instruction set (xscale).  I see an xscale package in the eCos I've
> checked out but it is not clear to me how I get from my current eCos
> configuration to one in which I can make calls from my C application
> to make use of the xscale instruction set.  I would appreciate any
> hints.  Thanks!

Isn't this just a compiler issue? So long as the compile knows you are
using an xscale with these extra instructions, it should use them.

Look what flags are passed to the compiler, in particular march. 

If you want to explicitly call these xscale instructions, you will
need to do inline/out of line assembly language programming, or find a
library from somewhere which has wrapped them up in something easier
to use.

   Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2007-11-14 13:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 18:54 [ECOS] networking support for my eCos application C B
2007-11-02 19:08 ` Gary Thomas
2007-11-05 16:12   ` C B
2007-11-05 18:43     ` Andrew Lunn
     [not found]       ` <BAY105-W2585C1EB05E16C54EA73C5EA890@phx.gbl>
2007-11-06  8:34         ` Andrew Lunn
2007-11-08 20:01   ` C B
2007-11-08 21:05     ` Andrew Lunn
2007-11-09  9:22     ` [ECOS] " John Dallaway
2007-11-09 13:32       ` [ECOS] " C B
2007-11-09 18:48         ` C B
2007-11-09 18:55           ` Andrew Lunn
2007-11-12 11:52             ` C B
2007-11-12 12:27               ` Gary Thomas
2007-11-12 18:11                 ` C B
2007-11-14 13:30                   ` [ECOS] Adding xscale support to my eCos config C B
2007-11-14 14:05                     ` Andrew Lunn [this message]
2007-11-14 14:13                       ` Mark Salter
2007-11-14 15:23                       ` C B
2007-11-14 15:24                         ` Gary Thomas
2007-11-14 20:11                           ` C B
2007-11-14 20:42                             ` C B
2007-11-16 18:15                               ` [ECOS] Performance timing C B
2007-11-16 19:47                                 ` Gary Thomas
2007-11-16 19:55                                   ` C B
2007-11-17  7:07                                     ` Mike Arthur
2007-11-19  5:19                                       ` C B
2007-11-19 14:36                                         ` Gary Thomas
2007-11-22 13:39                                           ` [ECOS] eCos compatible with arm-elf-gcc version 4.1.1? C B
2007-11-22 14:28                                             ` Lars Poeschel
2007-11-22 16:42                                               ` C B
2007-11-27 14:38                                               ` C B
2007-11-28 13:24                                                 ` C B
     [not found]             ` <BAY105-W28BEA5A1C91693C8BE5C8FEA870@phx.gbl>
2007-11-12 12:07               ` [ECOS] RE: networking support for my eCos application Andrew Lunn
2007-11-12 18:05                 ` C B

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=20071114133044.GX4401@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=csb_80@hotmail.com \
    --cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).