From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2484 invoked by alias); 22 Jun 2005 10:21:49 -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 2370 invoked by uid 22791); 22 Jun 2005 10:21:40 -0000 Received: from nproxy.gmail.com (HELO nproxy.gmail.com) (64.233.182.192) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 22 Jun 2005 10:21:40 +0000 Received: by nproxy.gmail.com with SMTP id d4so15120nfe for ; Wed, 22 Jun 2005 03:21:37 -0700 (PDT) Received: by 10.48.4.20 with SMTP id 20mr12597nfd; Wed, 22 Jun 2005 03:21:37 -0700 (PDT) Received: by 10.48.43.13 with HTTP; Wed, 22 Jun 2005 03:21:37 -0700 (PDT) Message-ID: <69dd805e050622032156184ef2@mail.gmail.com> Date: Wed, 22 Jun 2005 10:21:00 -0000 From: Fabian Scheler Reply-To: Fabian Scheler To: "K. Sinan YILDIRIM" Cc: ecos-discuss@sources.redhat.com In-Reply-To: <200506221006.59090.sinany@beko.com.tr> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200506221006.59090.sinany@beko.com.tr> Subject: Re: [ECOS] ECOS - MIPS X-SW-Source: 2005-06/txt/msg00200.txt.bz2 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. th= ere > must be a clean version of ecos that includes pure mips dependencies. atl= as > 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