From: "K. Sinan YILDIRIM" <sinany@beko.com.tr>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ECOS - MIPS
Date: Wed, 22 Jun 2005 07:09:00 -0000 [thread overview]
Message-ID: <200506221006.59090.sinany@beko.com.tr> (raw)
In-Reply-To: <W646741726646371119364845@webmail3>
i dont understand why ecos restricts its users with a configtool and
templates. i want a clean makefile and module structure. not structuring with
a config tool or hardware environment. it is really diffucult to add or
remove a new file. also many files are coupled each other.
i have a board that implements mips core and different to atlas board. there
must be a clean version of ecos that includes pure mips dependencies. atlas
dependencies makes people to change their OS choice...
does anyone think that it is really configurable ? i dont think so...
OS must fit the environment, environment must not.
Salı 21 Haziran 2005 05:40 ös tarihinde, rramesh@connextechnology.com şunları
yazmıştı:
> I attempted the same a couple of months ago and gave up. Looks like we need
> to have extensive changes to eCos before we can attempt that. The possible
> route to go is to use a Simulator. If you look in the source directories,
> there is a simulator which fakes the board related initializations, drivers
> etc. Attempt that. If I recall right, I could not attempt to compile it
> successfully. I posted a few messages here, did not get any response and I
> had to change the course of RTOS selection for my project. Hope this helps.
> If you find any help in this regard - in private- would you be kind enough
> to inform me as well? Thanks and regards
> Ramesh
>
> > -----Original Message-----
> > From: K. Sinan YILDIRIM [mailto:sinany@beko.com.tr]
> > Sent: Tuesday, June 21, 2005 01:38 PM
> > To: ecos-discuss@sources.redhat.com
> > Subject: [ECOS] ECOS - MIPS
> >
> > 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
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next parent reply other threads:[~2005-06-22 7:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <W646741726646371119364845@webmail3>
2005-06-22 7:09 ` K. Sinan YILDIRIM [this message]
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 15:28 ` [ECOS] " Grant Edwards
2005-06-24 6:14 ` K. Sinan YILDIRIM
2005-06-24 9:07 ` Nick Garnett
2005-06-24 14:08 ` Grant Edwards
2005-06-24 14:52 ` K. Sinan YILDIRIM
2005-06-24 16:39 ` Grant Edwards
2005-06-23 16:19 ` [ECOS] " Richard Forrest
2005-06-24 0:04 ` [ECOS] " Grant Edwards
2005-06-24 7:48 ` Richard Forrest
2005-06-23 15:17 ` Grant Edwards
2005-06-21 13:40 [ECOS] " K. Sinan YILDIRIM
2005-06-21 13:53 ` Andrew Lunn
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=200506221006.59090.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).