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

On 22-Jan-2001 Fano Ramparany wrote:
> Gary Thomas wrote:
> 
>> Here's the very simplest way to test this (using ecosconfig).
>>
>>   [gthomas@hermes test2]$ ecosconfig new edb7212 net
>>   [gthomas@hermes test2]$ ecosconfig tree
>>   [gthomas@hermes test2]$ make;make -C net/tcpip/current/ tests TESTS=tests/ping_test
>>
>> Similar results can be obtained by just using the "net" template and
>> then enabling/building tests.
>>
>> Does this sequence [scenario] not work for you?
> 
> I guess this is the linux scenario. We are using the Windows Development tools.
> Thus here is our scenario:
> We have registered the Networking package using the Package Administration tool, then
> using the eCos Configuration tool we have added the Networking package by ticking on
> INET support option.
> Initialization options for eth0 and eth1 are greyed out, then we can't modify them.
> There
> status are: Use BOOTP/DHCP and Show BOOTP/DHCP for both eth0 and eth1.
> Other options have been set with their default value.
> Then we've build the library and the tests.
> When running the ping test here is the gdb debugger trace, which makes no mention of the
> ping
> session I think:
>

The way I did this using the Windows Config Tool was
  Build->Templates
    Hardware = Cirrus Logic development board
    Packages = net

This selection is equivalent to the 'ecosconfig' steps above.  All of the appropriate
options are automatically enabled and it should "just work".

  reply	other threads:[~2001-01-22  7:13 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 [this message]
2001-01-30  2:52       ` Fano Ramparany
2001-01-30  4:34         ` Gary Thomas
2001-01-30  6:03           ` Fano Ramparany
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=XFMail.20010122081252.gthomas@cambridge.redhat.com \
    --to=gthomas@cambridge.redhat.com \
    --cc=Fano.Ramparany@rd.francetelecom.fr \
    --cc=ecos-discuss@sourceware.cygnus.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).