public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@ecoscentric.com>
To: Raghavendar Mani <raghav82@gmail.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Porting SCTP to eCos
Date: Thu, 19 May 2005 04:24:00 -0000	[thread overview]
Message-ID: <m3acmsfpwo.fsf@xl5.calivar.com> (raw)
In-Reply-To: <5e53687005051807385e038897@mail.gmail.com>

Raghavendar Mani <raghav82@gmail.com> writes:

> hi
>    iam involoved in porting SCTP(stream control transmission protocol)
>    to eCos. inorder to include the SCTP into the N/w package of eCos
>    what procdures i need to follow. LKSCTP kernel implementation for
>    linux environment is avalaible. What constraints i have look in for
>    to implement it.
>    i hope to get valuable informations. 

I doubt very much that you will be able to get LKSCTP to work in the
eCos TCP/IP stack. The eCos stack is based on FreeBSD, which is a
completely different implementation to the Linux stack.

There would also be licensing issues to consider.

While there are some SCTP patches for the FreeBSD stack, they are for
more recent versions that we have.

Your best approach would be to find a user-space SCTP implementation,
and port that to eCos.


-- 
Nick Garnett                                     eCos Kernel Architect
http://www.ecoscentric.com                The eCos and RedBoot experts


-- 
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:[~2005-05-18 16:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18 23:13 Raghavendar Mani
2005-05-19  4:24 ` Nick Garnett [this message]
     [not found] <5e53687005051821301bec78b4@mail.gmail.com>
     [not found] ` <3b2187af03ada193c609ecb44d376857@micmac.franken.de>
2005-05-20 10:44   ` Raghavendar Mani
2005-05-20 13:43     ` Nick Garnett
2005-05-23  9:21       ` Randall Stewart

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=m3acmsfpwo.fsf@xl5.calivar.com \
    --to=nickg@ecoscentric.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=raghav82@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).