From: Colin Ford <colin.ford@pipinghotnetworks.com>
To: Ecos Mailing List <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Linux Synthetic Target TCP/IP Support
Date: Thu, 07 Sep 2000 02:57:00 -0000 [thread overview]
Message-ID: <39B76736.C1581C11@pipinghotnetworks.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1755 bytes --]
Hello All,
I'm a new user to eCos and have just managed to get
it running on our MIPS board. I downloaded the version
1.3.1 from the red hat site and also downlaoded the
net1.0b1.epk from the site.
I have a few questions:
Q) Does the synthetic target for Linux have support
     for the TCP/IP stack?
Â
     I 'make tests' and get errors when making
     the net tests for linux:
     ECOS/linux/install/include/lib/libkern/libkern.h:107:
parse error before `max'
     ECOS/linux/install/include/lib/libkern/libkern.h:107:
warning: type defaults to `int' in declaration of `max'
     ECOS/linux/install/include/lib/libkern/libkern.h:107:
warning: parameter names (without types) in function declaration
     ECOS/linux/install/include/lib/libkern/libkern.h:107:
warning: data definition has no type or storage class
     Do I have to write a psudo ethernet driver
for the
      synthetic target, or has someone
already done
      this?
Q) Is it better to download eCos using CVS ? If so how
     offten should this be done? Plus are
there major
     inprovments in the version on the red
hat site to that
     held in the CVS repository? Plus
are there any
     instructions for doing this?
I'm sorry if these questions are in some FAQ someone
but I could not find it.... :-(
Many thanks for any help,
Col.
Â
--Â
===========================================
Colin Ford              PipingHot Networks
Software Engineer       +44 (0)1364 655510
Â
reply other threads:[~2000-09-07 2:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=39B76736.C1581C11@pipinghotnetworks.com \
--to=colin.ford@pipinghotnetworks.com \
--cc=ecos-discuss@sources.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).