From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24443 invoked by alias); 22 Dec 2007 10:59:29 -0000 Received: (qmail 24306 invoked by uid 22791); 22 Dec 2007 10:59:28 -0000 X-Spam-Check-By: sourceware.org Received: from 204-133-123-27.dia.static.slbbi.com (HELO mail.chez-thomas.org) (204.133.123.27) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 22 Dec 2007 10:59:23 +0000 Received: by mail.chez-thomas.org (Postfix, from userid 999) id DF58D195022A; Sat, 22 Dec 2007 03:59:21 -0700 (MST) Received: from [192.168.1.101] (hermes_local [192.168.1.101]) by mail.chez-thomas.org (Postfix) with ESMTP id 0EE9819500CE; Sat, 22 Dec 2007 03:59:20 -0700 (MST) Message-ID: <476CEE07.5010303@mlbassoc.com> Date: Sat, 22 Dec 2007 17:19:00 -0000 From: Gary Thomas User-Agent: Thunderbird 1.5.0.12 (X11/20070530) MIME-Version: 1.0 To: Gregg Levine CC: ecos-discuss@ecos.sourceware.org References: <18d205ed0712211848y3e537308gd4257986b153338b@mail.gmail.com> In-Reply-To: <18d205ed0712211848y3e537308gd4257986b153338b@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] creating a new template X-SW-Source: 2007-12/txt/msg00143.txt.bz2 Gregg Levine wrote: > Hello! > In the collections of templates I see three Intel386 based PC ones. I > would like to create one that contains everything except networking by > means of the preselected devices. > > Can anyone suggest the steps needed? > Firstly, you probably mean "target", not "template". Targets are ways of instantiating a particular hardware platform (architecture, 'motherboard', devices, etc). Templates describe collections of software packages and are hardware neutral. For example, the 'pc_i82559' target describes a generic PC which has, in particular, hardware support for the Intel 82559 PCI ethernet controller. If you build eCos like this: % ecosconfig new pc_i82559 minimal % ecosconfig tree % make the resulting eCos kernel will run on that PC [box], but since the template used (minimal) does not include any networking support packages, the fact that the target specified the i82559 driver is irrelevant. In fact, you would get an identical eCos kernel from % ecosconfig new pc_i82544 minimal % ecosconfig tree % make Given the way that CDL is used to enable/disable the building of drivers, etc, the ethernet drivers in either of these examples won't even be built. If you don't want networking, then don't use a template which includes network support. If you examine the templates, you'll see that only 'net', 'lw_ip' and 'all' include networking. If you start with any other template, you have to explicitly add network support, regardless of what hardware device drivers the particular target may support. -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss