public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "K. Sinan YILDIRIM" <sinany@beko.com.tr>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] ECOS - MIPS
Date: Tue, 21 Jun 2005 13:40:00 -0000	[thread overview]
Message-ID: <200506211638.23121.sinany@beko.com.tr> (raw)

hi!

I examined the MIPS platform ports for Ecos. I have some problems and i am a 
little bit confused.

As far as i see, we cannot configure or compile ecos without selecting a 
target platform. One of the Mips targets i examined was Atlas board. when i 
configure ecos with configtool, it generates a buildtree with the atlas board 
spesific headers. 

Is there a possible way to configure ecos without using a target platform ? or 
jusy empty macros or platform specific functions? I want to have a clean and 
a MIPS ported code and then fill these functions according to my board. Is 
there a way to do this ?  I dont want to inspect atlas board specific codes 
or compile atlas platform files.

please help me... i really need help!


-- 
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:[~2005-06-21 13:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 13:40 K. Sinan YILDIRIM [this message]
2005-06-21 13:53 ` Andrew Lunn
     [not found] <W646741726646371119364845@webmail3>
2005-06-22  7:09 ` K. Sinan YILDIRIM
2005-06-22 10:21   ` Fabian Scheler
2005-06-22 18:28   ` L D
2005-06-23  6:29     ` K. Sinan YILDIRIM
2005-06-23  7:03       ` Andrew Lunn
     [not found]         ` <200506231102.17394.sinany@beko.com.tr>
2005-06-23  8:07           ` K. Sinan YILDIRIM
2005-06-23  8:34             ` Jerome Souquieres
2005-06-23  9:02             ` Andrew Lunn
2005-06-23 10:27               ` K. Sinan YILDIRIM
2005-06-23 16:19                 ` Richard Forrest

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=200506211638.23121.sinany@beko.com.tr \
    --to=sinany@beko.com.tr \
    --cc=ecos-discuss@sources.redhat.com \
    /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).