From: Nick Garnett <nickg@ecoscentric.com>
To: Raghavendar Mani <raghav82@gmail.com>
Cc: ecos-discuss@sources.redhat.com, randall@stewart.chicago.il.us,
amassa@san.rr.com
Subject: Re: [ECOS] Porting SCTP to eCos
Date: Fri, 20 May 2005 13:43:00 -0000 [thread overview]
Message-ID: <m3br76ckso.fsf@xl5.calivar.com> (raw)
In-Reply-To: <5e53687005052001173901171a@mail.gmail.com>
Raghavendar Mani <raghav82@gmail.com> writes:
> hi,
> iam involved in the project of Proting SCTP to eCos
> Whether it is possible to include sctplib a userland
> implementation on eCos.
> when i enquired with SCTPLIB developers, they say
> " sctplib should be portable if eCos supports raw sockets.Since ecos
> has a FreeBSD network kernel you might consider to port the SCTP
> stack, which is part of the KAME project".
>
> may i know which r raw sockets, ecos supports it.
> Can i get a detail report Pl.
eCos has support for raw sockets, it is currently used in the ping
tests.
The KAME project SCTP work provides an in-kernel implementation, but
is for a later version of the BSD stack than we support. It would
probably require a complete reimport of the BSD stack into 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
next prev parent reply other threads:[~2005-05-20 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2005-05-23 9:21 ` Randall Stewart
2005-05-18 23:13 Raghavendar Mani
2005-05-19 4:24 ` Nick Garnett
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=m3br76ckso.fsf@xl5.calivar.com \
--to=nickg@ecoscentric.com \
--cc=amassa@san.rr.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=raghav82@gmail.com \
--cc=randall@stewart.chicago.il.us \
/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).