From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Mandeep Sandhu <mandeepsandhu.chd@gmail.com>
Cc: ecos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] ecos + lwip
Date: Thu, 30 Jul 2009 13:51:00 -0000 [thread overview]
Message-ID: <20090730135202.GA15289@sg-ubuntu.local> (raw)
In-Reply-To: <b18c5f790907300610u2b0365cdof673f89bb2fde0f5@mail.gmail.com>
Mandeep Sandhu wrote:
> I'm using ecos-3.0 for current work.
>
> How do you check the version of lwip that ships alongwith this version
> of ecos? I'm looking at the Changelog file for this info.
>
> The Changelog shows the current version as 1.1.1 whereas the latest
> stable version of lwip released is 1.3.0.
AFAIK, the eCos 3.0/CVS lwIP is something likes lwIP 1.1.0 +.
> Are there any major issues with 1.1.1 ? (it's seems pretty dated)
The latest lwIP 1.3.X has issues with PPP
http://cvs.savannah.gnu.org/viewvc/lwip/CHANGELOG?root=lwip&view=markup
> Are people using this in production code?
STFW
http://en.wikipedia.org/wiki/LwIP
Altera, Analog Devices, Xilinx, etc. use lwIP.
> Also, I plan to implement a limited DHCP server. Are "raw sockets" the
> only option available? Has anybody used lwip's raw native API to do
> similar stuff?
I'm sorry, I do not know about.
Sergei
--
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:[~2009-07-30 13:51 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 13:10 Mandeep Sandhu
2009-07-30 13:51 ` Sergei Gavrikov [this message]
2009-07-31 5:44 ` Mandeep Sandhu
2009-07-31 18:56 ` Sergei Gavrikov
2009-08-02 17:24 ` Mandeep Sandhu
2009-08-26 11:01 Mandeep Sandhu
2009-08-26 11:16 ` Simon Kallweit
2009-08-27 10:49 ` Mandeep Sandhu
2009-08-27 11:17 ` Simon Kallweit
2009-08-27 12:42 ` Mandeep Sandhu
2009-08-27 13:20 ` Mandeep Sandhu
2009-08-27 13:42 ` Simon Kallweit
2009-08-27 13:51 ` Mandeep Sandhu
2009-08-27 14:02 ` Mandeep Sandhu
2009-08-27 14:06 ` Simon Kallweit
2009-08-27 14:47 ` Sergei Gavrikov
2009-08-27 15:03 ` Sergei Gavrikov
2009-09-01 12:04 ` Mandeep Sandhu
2009-09-01 12:17 ` Simon Kallweit
2009-09-01 12:32 ` Mandeep Sandhu
2009-09-01 12:38 ` Simon Kallweit
2009-09-01 12:49 ` Mandeep Sandhu
2009-09-01 12:57 ` Simon Kallweit
2009-09-01 13:25 ` Mandeep Sandhu
2009-09-01 13:34 ` Simon Kallweit
2009-09-01 15:20 ` Mandeep Sandhu
2009-09-01 15:32 ` Simon Kallweit
2009-09-01 15:46 ` Mandeep Sandhu
2009-09-01 15:49 ` Simon Kallweit
2009-09-02 6:15 ` Mandeep Sandhu
2009-09-02 13:19 ` Mandeep Sandhu
2009-09-02 15:32 ` Simon Kallweit
2009-09-03 7:45 ` Mandeep Sandhu
2009-09-03 8:36 ` Simon Kallweit
2009-09-03 8:46 ` Mandeep Sandhu
2009-09-03 8:48 ` Simon Kallweit
2009-09-03 8:55 ` Mandeep Sandhu
2009-09-03 9:04 ` Simon Kallweit
2009-09-03 10:23 ` Mandeep Sandhu
2009-09-03 10:46 ` Sergei Gavrikov
2009-08-27 13:52 ` Sergei Gavrikov
2009-08-27 14:05 ` Simon Kallweit
2009-08-27 14:42 ` Bart Veer
2009-08-27 14:54 ` Sergei Gavrikov
2009-08-27 13:45 ` Sergei Gavrikov
2009-08-27 13:49 ` Mandeep Sandhu
2009-08-27 14:04 ` Simon Kallweit
[not found] <144735.17263.qm@web65404.mail.ac4.yahoo.com>
2009-08-27 14:11 ` Simon Kallweit
2009-08-27 14:20 agfa prayoga s
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=20090730135202.GA15289@sg-ubuntu.local \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=mandeepsandhu.chd@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).