public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Gregg Levine <gregg.drwho8@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] creating a new template
Date: Sat, 22 Dec 2007 17:19:00 -0000	[thread overview]
Message-ID: <476CEE07.5010303@mlbassoc.com> (raw)
In-Reply-To: <18d205ed0712211848y3e537308gd4257986b153338b@mail.gmail.com>

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

  reply	other threads:[~2007-12-22 10:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-22 17:13 Gregg Levine
2007-12-22 17:19 ` Gary Thomas [this message]
2007-12-23  4:09   ` Gregg Levine
2007-12-23  5:05     ` Gary Thomas
2007-12-23  8:28       ` Gary Thomas
2007-12-23 16:07 Gregg Levine

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=476CEE07.5010303@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gregg.drwho8@gmail.com \
    /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).