public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Fabian Scheler <fabian.scheler@gmail.com>
To: "K. Sinan YILDIRIM" <sinany@beko.com.tr>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ECOS - MIPS
Date: Wed, 22 Jun 2005 10:21:00 -0000	[thread overview]
Message-ID: <69dd805e050622032156184ef2@mail.gmail.com> (raw)
In-Reply-To: <200506221006.59090.sinany@beko.com.tr>

Hi,

> 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.

eCos is, compared to other embedded OS, a really highly configurable
OS, the configtool and templates are provided to support the user when
selecting an appropriate set of options that fulfill his needs. I
don't believe you want to manage the selction of the numerous features
on your own. In my opinion eCos is not really useable without the
configtool

> 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...

well, eCos does (and you can find them in packages/hal/mips/arch I
think), the other directories you can see are containing
board-specific stuff). Well, and if eCos is not available for the
special board you use, you have to adopt an existing board package,
and that's the case with every embedded OS, because different boards
have different features and thus they need a (at least partly)
specific HAL.

Ciao, Fabian

--
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-22 10:21 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
2005-06-22 10:21   ` Fabian Scheler [this message]
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=69dd805e050622032156184ef2@mail.gmail.com \
    --to=fabian.scheler@gmail.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=sinany@beko.com.tr \
    /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).