From: Rohit <will.u.tellmemore@gmail.com>
To: "Mike Arthur" <arth2219@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Project ideas for graduate course
Date: Tue, 31 Jul 2007 07:34:00 -0000 [thread overview]
Message-ID: <97993dc40707310034x25be6389t743929d93f368152@mail.gmail.com> (raw)
In-Reply-To: <2a3305fe0707301026l128193f5ib904b30c5c7081b9@mail.gmail.com>
Thanks a lot for your suggestion. I would go through what you have
suggested and let you guys know what i select out of these(or
something different). More suggestions are still welcome though.
On 7/30/07, Mike Arthur <arth2219@gmail.com> wrote:
> Try comparing the features another RTOS has which eCos lacks. RTEMS
> is another open source RTOS that has some features that would be nice
> to see in eCos:
>
> http://www.rtems.com/wiki/index.php/RTEMSFeatures
>
> A few of the features I'd like to see are RPC, NFS, a syslog client,
> and the ability to dynamically link in modules. You could port code
> over from other systems for the first three items. You'll want to
> check the license on any code you port though.
>
> Hope this helps,
> Mike
>
>
>
> On 7/30/07, Rohit <will.u.tellmemore@gmail.com> wrote:
> > Hi All,
> > I am a computer science graduate from India and i would like to do
> > my graduate project work on eCos but i am new to eCos world. Will you
> > please suggest me some good ideas that i can start thinking about ??
> > Any information about this will be highly appreciated. Links to
> > existing but unfinished projects would also be fine.
> >
> >
> > Thanks,
> > Rohit
> >
> > --
> > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> >
> >
>
--
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:[~2007-07-31 7:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 13:36 Rohit
2007-07-30 17:26 ` Mike Arthur
2007-07-31 7:34 ` Rohit [this message]
2007-07-31 9:35 ` Andrew Lunn
2007-07-31 9:50 ` Klaas Gadeyne
2007-07-31 10:01 ` Andrew Lunn
2007-07-31 11:17 ` Klaas Gadeyne
2007-07-31 12:12 ` Andrew Lunn
2007-07-31 12:36 ` Klaas Gadeyne
2007-07-31 13:01 ` Andrew Lunn
2007-08-01 8:04 ` Klaas Gadeyne
2007-08-01 10:09 ` Andrew Lunn
2007-08-01 12:14 ` Klaas Gadeyne
2007-08-01 12:31 ` Andrew Lunn
2007-08-02 11:39 ` Klaas Gadeyne
2007-07-31 14:31 ` [ECOS] " Grant Edwards
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=97993dc40707310034x25be6389t743929d93f368152@mail.gmail.com \
--to=will.u.tellmemore@gmail.com \
--cc=arth2219@gmail.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).