From: Simon Kallweit <simon.kallweit@intefo.ch>
To: ganesh kr <krganesh01@gmail.com>, John Dallaway <john@dallaway.org.uk>
Cc: eCos developers <ecos-devel@ecos.sourceware.org>
Subject: lwip 1.3.2 port
Date: Fri, 22 Jan 2010 12:54:00 -0000 [thread overview]
Message-ID: <4B599FDA.7020808@intefo.ch> (raw)
In-Reply-To: <73f9997f1001220342h7bc1c79cl7180a184bee867f3@mail.gmail.com>
Hi John,
Hi Ganesh
Nice to hear that you are using the lwip stack and it is working fine
for you. Currently, I hold the lwip code in my own git repo, shared with
other changes I have done to eCos. The plan was to get my current lwip
code into the CVS. John, I think it's about time to get this done. I can
do one latest merge with the lwip 1.3.2 codebase and then we should be
ready.
I still have some local changes concerning ppp in my repo (which are
absolutely necessary in my current project). But I think we should keep
these changes in for a while. It seems like some work is done in the
official lwip repo, concerning ppp. But these changes will only be
available in future 1.4.x releases. The current stable release is 1.3.2,
and will be for a little while. When we get to a stable 1.4.x release,
it may be a good time to get back to the lwip repositories ppp code. In
the meanwhile, I'll keep track of what's happening in the official repo
and try to incorporate my changes into the official repo (support for
ppp in a single-threaded lwip environment).
What do you think?
Simon
ganesh kr wrote:
> Hi Simon,
>
> I am using the lwip 1.3.0 stack ported to ecos 3.0 by you for the last
> 4-5 monts and is working fine. Thanks for that. I have some questions:
> 1. Are you keeping it in any repository so that I can take the latest
> one? The one which I am using is lwip-20090722.tar.gz
> 2. What I need to do to keep the codebase provided by you to be in
> sync with the latest developments/fixes heppening in lwip1.3.0
>
> Regards,
> Ganesh K R
>
> On Wed, Jul 22, 2009 at 4:58 PM, Simon Kallweit
> <simon.kallweit@intefo.ch> wrote:
>> ganesh kr wrote:
>>> Hi,
>>>
>>> I am new to ecos. I have 258 KB flash on my board. I am able to build
>>> and run my small appliaction with ecos + lwip as nw stack. the code
>>> size is 69KB.
>>> I want to switch to freebsd/ openbsd based nw stack so that I can use
>>> SNMP and DNS. Please any one let me know the aproximate code siaze if
>>> I use freebsd based nw stack.
>> I don't have much experience with the other stacks (using lwip myself) but
>> you need plenty of RAM to use them, which could be a problem on your
>> platform. lwip does have support for DNS and SNMP, the APIs just differ. You
>> could check out my current lwip port, which is a lot more up to date than
>> the one in the eCos repository:
>>
>> http://download.westlicht.ch/lwip-20090722.tar.gz
>>
>> Simon
>>
next parent reply other threads:[~2010-01-22 12:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <73f9997f0907192203h77494e62u58b44ccfc7a738f4@mail.gmail.com>
[not found] ` <4A65B8AE.8090204@martinlaabs.de>
[not found] ` <73f9997f0907212153i743cfc7as86d2a1205c5dc7ab@mail.gmail.com>
[not found] ` <73f9997f0907220421y145a62c3lb2728a132474c900@mail.gmail.com>
[not found] ` <4A66F7E0.4050703@intefo.ch>
[not found] ` <73f9997f1001220342h7bc1c79cl7180a184bee867f3@mail.gmail.com>
2010-01-22 12:54 ` Simon Kallweit [this message]
2010-01-22 13:31 ` John Dallaway
2010-01-22 14:43 ` Simon Kallweit
2010-01-22 18:51 ` John Dallaway
2010-01-23 11:57 ` Simon Kallweit
2010-01-23 14:04 ` John Dallaway
2010-01-23 15:46 ` Simon Kallweit
2010-01-25 11:44 ` John Dallaway
2010-01-25 16:35 ` Simon Kallweit
2011-05-08 8:11 ` lwIP 1.4.0 port planning [ was Re: lwip 1.3.2 port ] John Dallaway
2011-06-07 20:28 ` Ilija Kocho
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=4B599FDA.7020808@intefo.ch \
--to=simon.kallweit@intefo.ch \
--cc=ecos-devel@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
--cc=krganesh01@gmail.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).