From: Raghavendar Mani <raghav82@gmail.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Porting SCTP to eCos
Date: Wed, 18 May 2005 23:13:00 -0000 [thread overview]
Message-ID: <5e53687005051807385e038897@mail.gmail.com> (raw)
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.
wishes
Raghav
--
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 reply other threads:[~2005-05-18 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 23:13 Raghavendar Mani [this message]
2005-05-19 4:24 ` Nick Garnett
[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=5e53687005051807385e038897@mail.gmail.com \
--to=raghav82@gmail.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).