public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Robin Randhawa <robin.randhawa@gmail.com>
To: Alok Singh <aloks@broadcom.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Net BSD network stack posix tasks -
Date: Tue, 29 May 2007 17:26:00 -0000	[thread overview]
Message-ID: <1180459242.6313.59.camel@blackpearl> (raw)
In-Reply-To: <FE7FB54DCB7C6949A1D3F9FF22DA6C135AAF0E@lvl7in-mail01.lvl7.com>

Greetings.

Your description is quite puzzling. 

POSIX threads in eCos have nothing to do with the network stack, not
directly at least. The POSIX functionality is essentially a carefully
crafted set of wrappers over the basic eCos threading architecture.

Think of the networking stack as a state machine implementation borrowed
from a BSD derivative and driven using native eCos threads running under
the eCos kernel.

Now you can take a POSIX application and via the POSIX "wrapper" link
the application to the networking stack and the kernel.

My humble and pointed suggestion : RTFM.
eCos has abundant documentation that sheds light on these concepts.

Cheerio!
Robin

On Tue, 2007-05-29 at 22:35 +0530, Alok Singh wrote:
> Hi,
> I don't understand licensing issues much. I've a question. Am I allowed
> to convert network stack threads to posix threads instead of native cyg
> threads?   I've compatibility issues making ecos network stack work with
> my application (Posix based.) Though there are ways to overcome this
> issue, but they affect the performance of the system.
> 
> 
> regards,
> Alok
> 
> 


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2007-05-29 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 17:11 Alok Singh
2007-05-29 17:20 ` Gary Thomas
2007-05-29 17:26 ` Robin Randhawa [this message]
2007-05-30  0:00 ` Nick Garnett
2007-05-30 11:59   ` Alok Singh
2007-05-30 13:07     ` Gary Thomas
2007-05-30 15:42       ` Alok Singh
2007-05-30 15:56         ` Gary Thomas
2007-05-30 16:33           ` Andrew Lunn
2007-05-30 17:53             ` Alok Singh
2007-05-30 18:14               ` Andrew Lunn

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=1180459242.6313.59.camel@blackpearl \
    --to=robin.randhawa@gmail.com \
    --cc=aloks@broadcom.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).