public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: "K. Sinan YILDIRIM" <sinany@beko.com.tr>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ECOS - MIPS
Date: Thu, 23 Jun 2005 07:03:00 -0000	[thread overview]
Message-ID: <20050623070257.GB26538@lunn.ch> (raw)
In-Reply-To: <200506230927.33072.sinany@beko.com.tr>

On Thu, Jun 23, 2005 at 09:27:32AM +0300, K. Sinan YILDIRIM wrote:
> People may have positive and negative comments about a SW product. Does this 
> group for only positive ones ? Or only positive questions ? 
> 
> I have been writing SW for about 10 years. I have just examined eCOS and found 
> that it is configurable on some way and unconfigurable ( hard to reconfigure 
> ) on some way. May be it is much more configurable than the existing ones but 
> not a super really configurable OS. 
> 
> I am the user. This is a user point of view . Having a seperate HAL layer or a 
> structured file tree doesnt make an operating system really configurable. 
> Configurability means to change the operating system according to your needs 
> in a quick way : not being able to change it in a month... 
> 
> configurable modern SW is done with SW patterns. Architectural and Design 
> patterns makes SW configurable, easy to change, etc... Embedded SW needs good 
> architectural design with really reusable architectural and design patterns. 
> What makes JAVA popular is these points. It is a programming framework that 
> fullfills these points.
> 
> eCOS is  not a really framework. When you read the documentation, it seems to 
> be an OS framework but indeed it doesn't. 
> 
> What i try to mean is we must make it better in order to make it usable in the 
> future. 

Could you give some examples of what you would change?

        Thanks
                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:[~2005-06-23  7:03 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
2005-06-22 18:28   ` L D
2005-06-23  6:29     ` K. Sinan YILDIRIM
2005-06-23  7:03       ` Andrew Lunn [this message]
     [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=20050623070257.GB26538@lunn.ch \
    --to=andrew@lunn.ch \
    --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).