public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: Gary Thomas <gthomas@cambridge.redhat.com>
Cc: eCos Disuss <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] network support
Date: Tue, 30 Jan 2001 06:43:00 -0000	[thread overview]
Message-ID: <4.3.2.7.2.20010130093013.00b19e20@larwe.com> (raw)
In-Reply-To: <XFMail.20010130073110.gthomas@cambridge.redhat.com>

> >> > I'm using the distribution version (v1.3.1 release for eCos and
> >>
> >>incredibly old - in fact, I don't even think they have network support
> >>for the Cirrus Logic board in them (they date from March 2000 or so)!!
> >
> > They don't have any network support in them at all, I understood that was
> > in the net-1.0b1 archive. I have that installed, but haven't tried to do
>
>The net.epk file will add the basic networking, but I'm pretty sure that it
>does not add any/all of the drivers for the various architectures.

Well, when I added it (manually, it wouldn't work with the graphical 
configuration tool), I got a new package "Cirrus Logic ethernet driver", 
description "Ethernet driver for Cirrus EDB7xxx development boards".

> > now; I haven't yet been able to compile anything I ever downloaded 
> using CVS).
>
>Have you actually tried building eCos from anonCVS (or is this just your
>experience in general)?  Most of our users are using anonCVS and I know of
>no problems with it.

Well, it is my experience in general. When I was trying to get a working 
set of ARM tools to compile eCos, I tried getting all the latest - gcc as 
well as eCos - and failed miserably with all sorts of errors I didn't have 
time to analyze. I prefer to wait for someone to archive up his working 
source tree, call it a snapshot, and make it available for download. It 
also means I don't have to wrestle with the cvs client program.

The eCos version I'm running brings up the board OK, and that's good enough 
for the working demo I need to show next week. I've been working on 
optimizing my DOS and ISO9660 filesystems, and porting my JPEG and MPEG-1 
decoders, and that has kept me happily occupied.

The product I'm working on right now is the low-end version that doesn't 
use networking, so I don't see any reason to try to jump through blazing 
hoops to get the latest greatest eCos version downloaded and working. It 
will probably go to manufacturing with 1.3.1 in it.

The higher-end versions with Ethernet.. well, I'll cross that bridge when I 
come to it.

=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/

"Und setzet ihr nicht das Leben ein,
Nie wird euch das Leben gewonnen sein."

  reply	other threads:[~2001-01-30  6:43 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
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 [this message]
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=4.3.2.7.2.20010130093013.00b19e20@larwe.com \
    --to=larwe@larwe.com \
    --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).