From: Durgaprasad Chivukula <durgaprasad.chivukula@gmail.com>
To: jani@iv.ro
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Help regarding:installing tftp-hpa on ecos, using lwip instead of the default tcp/ip stack???
Date: Wed, 13 Jul 2005 13:29:00 -0000 [thread overview]
Message-ID: <ccf077f705071306294b2d3d0c@mail.gmail.com> (raw)
In-Reply-To: <ccf077f7050712051958635b8b@mail.gmail.com>
Hi ,
Please reply , if you guys have any idea about my problem .
1. Whether I can configure ecos and the tftp client & server packages
inside the ecos to use lwip (low weight ip ) instead of the default
tcp/ip stack ???
2.If its possible , please tell me how can I accomplish this .????
I would be thankful for any kind of suggestions
Regards
Durga
On 7/12/05, Durgaprasad Chivukula <durgaprasad.chivukula@gmail.com> wrote:
> Hi Thomas,
>
> Thanks for the reply
>
> On 7/12/05, Gary Thomas <gary@mlbassoc.com> wrote:
> > On Tue, 2005-07-12 at 13:58 +0200, Durgaprasad Chivukula wrote:
> > > Hi ,
> > >
> > > I am a newbie to ecos , I installed ecos checked out from the latest
> > > CVS on a PC (i386 ) with redhat linux 9.0 , I have few questions
> > > regarding ecos
> > >
> > > 1.Can I install the tftp-hpa-0.40 package on ecos , if so what changes
> > > I have to do in make file and other files inorder to install.
> > >
> > > 2.The thing is I am taking the (low weight ip) lwip port to ecos and
> > > make the tftp-hpa to use lwip to "get" and "put" files on ecos , is
> > > this possible to do so ? I want to say the tftp-hpa to use lwip ,
> > > instead of the default tcp/ip stack from ecos
> > > How can I accomplish this ? To say it in raw words I want to test
> > > tftp-hpa with lwip and not the default tcp/ip stack from OS
> > >
> > > I read from the ecos documentation that we can disable a feature and
> > > add new features to ecos , I mean a way of configuring the OS , is
> > > this possible to do so with the problems I mentioned above?
> > >
> > > Please give me some ideas to proceed in my problem.Any kind of
> > > suggestions are welcome
> >
> > Why do you want to install this package? eCos already has complete
> > TFTP client and server support available.
>
> The reason , I am installing this package is to get tftp/udp/ip stack
> running for my embedded system and I want to test this stack
> basically. So I took lwip and then the tftp-hpa and now want to test
> this as a whole whether the tftp -hpa uses lwip or not..?
>
> Is it possible.. to confugure ecos in such a way that it uses lwip for
> getting and putting files , using the tftp client and server from ecos
> , without the need to install tftp-hpa??? If its possible can I use
> the code that ecos provides for tftp client and server..???
>
>
> >
> > To answer the question more directly; porting *any* outside package
> > takes some thought and time. eCos is *not* Linux, and while it can
> > provide a POSIX environment, building for an embedded system requires
> > tuning of the sources, etc.
>
> I read that , ecos is not linux ..., and I did nget the exact meaning
> of the sentence in your reply " and while it can provide a POSIX
> environment, building for an embedded system requires tuning of the
> sources, etc. " Can you please clarify..?
>
>
>
>
>
>
> >
> > --
> > ------------------------------------------------------------
> > Gary Thomas | Consulting for the
> > MLB Associates | Embedded world
> > ------------------------------------------------------------
> >
> >
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2005-07-13 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 11:58 Durgaprasad Chivukula
2005-07-12 12:08 ` Gary Thomas
2005-07-12 12:20 ` Durgaprasad Chivukula
2005-07-13 13:29 ` Durgaprasad Chivukula [this message]
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=ccf077f705071306294b2d3d0c@mail.gmail.com \
--to=durgaprasad.chivukula@gmail.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jani@iv.ro \
/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).