public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Fano Ramparany <Fano.Ramparany@rd.francetelecom.fr>
To: eCos Disuss <ecos-discuss@sourceware.cygnus.com>
Cc: Gary Thomas <gthomas@cambridge.redhat.com>
Subject: Re: [ECOS] network support
Date: Tue, 30 Jan 2001 06:03:00 -0000	[thread overview]
Message-ID: <3A76CA3F.3EF6A8FA@rd.francetelecom.fr> (raw)
In-Reply-To: <XFMail.20010130053349.gthomas@cambridge.redhat.com>

Gary Thomas wrote:

> On 30-Jan-2001 Fano Ramparany wrote:
> > I then had a look at the configuration file.
> > Below is the part of the "ecc" file related the network
> > drivers. All variables related to the NET_DRIVERS are assigned
> > a 0 value.
> > In the (Windows NT) eCos Configuration Tool, the items Initialization
> > options for 'eth0', are greyed out, and thus can't be
> > modified.
> > Do you have any hint about what I'm doing wrong?
> >
>
> This is definitely your problem.  Did you create this configuration
> from scratch?  I just tried this, starting fresh, selecting the
> Cirrus Logic development board + "net" template - AT ONE TIME - and
> it came out perfectly.
>

I don't have the "net" package available as an option package in
the Build->Template... dialog box. Instead  I do
a Cirrus Logic development board + "all" template. Then I
do I Build->Packages.. and select the "Networking" package which
I "Add>>" to the configuration. This adds the Networking node in
the configuration tree (with thoses "initialization option for eth0"
subnodes greyed out).

May be the TCP/IP package installation was not properly made.
But what I did for this purpose was
Red Hat eCos -> Package Administration Tool
then click on "Add.." and select the "net-1.0b1.epk" from the
"Open eCos Package Files" file selector.
Is this OK?

Fano

>   Build->Templates->Hardware = Cirrus Logic Development Board
>                     Packages = net
>
> What sources are you building from?  If non anonCVS, then you might
> consider trying that.

I'm using the distribution version (v1.3.1 release for eCos and
v1.0b1 release for the TCP/IP stack).

  reply	other threads:[~2001-01-30  6:03 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-19  8:41 Fano Ramparany
2001-01-19  9:36 ` Gary Thomas
2001-01-22  6:48   ` Fano Ramparany
2001-01-22  7:13     ` Gary Thomas
2001-01-30  2:52       ` Fano Ramparany
2001-01-30  4:34         ` Gary Thomas
2001-01-30  6:03           ` Fano Ramparany [this message]
2001-01-30  6:08             ` Gary Thomas
2001-01-30  6:25               ` Lewin A.R.W. Edwards
2001-01-30  6:31                 ` Gary Thomas
2001-01-30  6:43                   ` Lewin A.R.W. Edwards
2001-02-13  5:55               ` Fano Ramparany
2001-02-13  6:20                 ` Gary Thomas
2001-02-14  2:44                   ` Fano Ramparany
2001-02-14  5:08                     ` Gary Thomas
2001-02-14  7:59                       ` Fano Ramparany
2001-02-14  8:24                         ` Gary Thomas
2001-02-14  9:12                           ` Lewin A.R.W. Edwards
2001-02-14  9:25                             ` Gary Thomas
2001-02-14  9:32                               ` Lewin A.R.W. Edwards
2001-02-14  9:40                                 ` Gary Thomas
2001-02-14 10:28                                   ` Robin Farine
2001-02-15  6:42                           ` Fano Ramparany
2001-01-22  7:15   ` Fano Ramparany
  -- strict thread matches above, loose matches on Subject: below --
2001-01-30  6:20 James Dabbs
1999-02-10 21:23 [ECOS] Network Support Zubin Burjor Sethna
     [not found] ` < 6006B52C37ABD211AB0900805FFE9D79169230@saturn.sg.adisys.com.au >
1999-02-12 19:57   ` David J. Fiddes
1999-02-10 18:37 Wendell Thompson
1999-02-11  9:45 ` Rick Leir
     [not found]   ` < 36C2F1F1.63DE@hymarc.com >
1999-02-14  7:02     ` David J. Fiddes
1999-02-09 11:01 Gordon McFadden
     [not found] ` < Pine.LNX.4.04.9902090702270.648-100000@mailhost.westsoft-systems.com >
1999-02-10 13:22   ` David J. Fiddes
1999-02-10 21:19     ` Brendan Simon
1999-02-06 13:48 weatp
     [not found] ` < 9902069183.AA918326790@mail.syntron.com >
1999-02-08  8:26   ` Bart Veer

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=3A76CA3F.3EF6A8FA@rd.francetelecom.fr \
    --to=fano.ramparany@rd.francetelecom.fr \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=gthomas@cambridge.redhat.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).