From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14956 invoked by alias); 23 Jun 2005 08:34:43 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 14945 invoked by uid 22791); 23 Jun 2005 08:34:40 -0000 Received: from reverse.completel.net (HELO io.kis.fr) (213.244.14.130) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 23 Jun 2005 08:34:40 +0000 Received: from io.kis.fr (localhost.localdomain [127.0.0.1]) by localhost.kis.fr (Postfix) with ESMTP id A38DE1B5CC; Thu, 23 Jun 2005 10:34:38 +0200 (CEST) Received: from [62.160.1.128] (unknown [62.160.1.128])by io.kis.fr (Postfix) with ESMTPid 395101B5CA; Thu, 23 Jun 2005 10:34:36 +0200 (CEST) Message-ID: <42BA741B.60103@kis.fr> Date: Thu, 23 Jun 2005 08:34:00 -0000 From: Jerome Souquieres User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: "K. Sinan YILDIRIM" Cc: ecos-discuss@sources.redhat.com References: <20050622182844.7476.qmail@web88210.mail.re2.yahoo.com> <20050623070257.GB26538@lunn.ch> <200506231102.17394.sinany@beko.com.tr> <200506231104.32693.sinany@beko.com.tr> In-Reply-To: <200506231104.32693.sinany@beko.com.tr> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-imss-version: 2.028 X-imss-result: Passed X-imss-scores: Clean:99.90000 C:2 M:3 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) Subject: Re: [ECOS] ECOS - MIPS X-SW-Source: 2005-06/txt/msg00219.txt.bz2 K. Sinan YILDIRIM wrote: > i wont make it configurable with make files. i would use object oriented > configurabilitiy. just inspect Java. > > you register classes, you program for interfaces, you use abstract > classes. > > just inspect bridge or adapter pattern. you will understand me. > > > Well, I'm afraid eCos is by philosophy and design NOT the right OS for this kind of run-time configurability. eCos is designed for embedded systems where the hardware is well known (you don't keep adding expansion boards from no-name taiwanese manufacturers), where run-time resources (memory, cpu) are scarce. In this context, compile-time configurabibity through #ifdefs and makefiles is a must. I'm using eCos myself on a MIPS target (IDT32334) and have been through the following steps: - find an existing HAL which was close to my actual hardware (here: idt79s334a) and modify it to match my hardware exactly. - build redboot with this HAL to start my system - carefully select packages and build an eCos tailored for my needs. Most OS for embedded systems I know use this philosophy (create a BSP/HAL, build the OS from selected packages using some kind of configurator). eCos "just" pushes one step further the configurability. Maybe you should look for an OS not dedicated to embedded systems if this is not the way you intend to work and you have plenty of RAM. Maybe some flavor of Linux ? -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss