From: Simon Kallweit <simon.kallweit@intefo.ch>
To: John Dallaway <john@dallaway.org.uk>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: lwip 1.3.1 testing
Date: Mon, 07 Dec 2009 13:41:00 -0000 [thread overview]
Message-ID: <4B1D05F5.8030901@intefo.ch> (raw)
In-Reply-To: <4B066E2F.50106@dallaway.org.uk>
John Dallaway wrote:
> Hi Simon
>
> Simon Kallweit wrote:
>
>>>>> One minor point: It would be very useful for the stack to report its
>>>>> own IP address on the diagnostic channel.
>>>> I'll try to implement this. I guess you're mainly talking about DHCP IPs
>>>> right?
>>> Yes, although it might sometimes also be helpful to confirm a static IP
>>> address.
>> I have implemented reporting of the netif configuration for both static
>> configuration and DHCP on the interfaces loopif, slipif and eth. This is
>> configurable by CYGFUN_LWIP_SHOW_NETIF_CONFIG which is now enabled by
>> default.
>
> Excellent. I would like to push through with final review and get your
> lwIP port checked in to CVS, replacing the existing lwIP 1.1.1 port. Is
> lwip-20091027.tar.gz still current or do you have further changes?
> Should I be comparing your package with the upstream lwIP 1.3.1 sources
> or is it now closer to lwIP 1.3.2 RC1?
Sorry for the late answer, I have been on holidays. I think we should
wait a few days for the lwIP 1.3.2 release. I'll merge the changes and
do a few tests so we have a good initial version for a CVS checkin. It
seems that some work has been done on the PPP code as well. I'll see how
it fits with my current port.
Simon
next prev parent reply other threads:[~2009-12-07 13:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 7:11 Simon Kallweit
2009-08-21 7:43 ` John Dallaway
2009-08-21 9:12 ` Edgar Grimberg
2009-08-21 18:43 ` Sergei Gavrikov
2009-08-24 20:18 ` Sergei Gavrikov
2009-08-25 6:09 ` Simon Kallweit
2009-08-25 7:41 ` Simon Kallweit
2009-08-25 12:08 ` Sergei Gavrikov
2009-08-25 20:33 ` Sergei Gavrikov
2009-08-26 6:38 ` Simon Kallweit
2009-08-26 8:43 ` Sergei Gavrikov
2009-08-26 20:46 ` Sergei Gavrikov
2009-08-27 7:17 ` Simon Kallweit
2009-08-27 8:03 ` Sergei Gavrikov
2009-10-25 16:46 ` John Dallaway
2009-10-26 13:00 ` Simon Kallweit
2009-10-26 13:54 ` John Dallaway
2009-10-26 14:29 ` Simon Kallweit
2009-10-26 17:13 ` John Dallaway
2009-10-27 13:06 ` Simon Kallweit
2009-11-20 10:24 ` John Dallaway
2009-12-07 13:41 ` Simon Kallweit [this message]
2009-12-17 10:45 ` John Dallaway
2010-01-19 12:07 ` John Dallaway
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=4B1D05F5.8030901@intefo.ch \
--to=simon.kallweit@intefo.ch \
--cc=ecos-devel@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/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).