public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001873] Patches to upgrade lwip to 1.4.1 Date: Fri, 06 Sep 2013 07:01:00 -0000 [thread overview] Message-ID: <bug-1001873-13-ipyJEoz9bX@http.bugs.ecos.sourceware.org/> (raw) In-Reply-To: <bug-1001873-13@http.bugs.ecos.sourceware.org/> Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001873 Will Wagner <willw@carallon.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |MODIFIED --- Comment #23 from Will Wagner <willw@carallon.com> --- (In reply to comment #21) > Will, the complete diff against existing eCos sources looks clean. > > Can you let me know which significant lwIP features you have exercised using > this codebase? For example, which protocols, interfaces and APIs? In our code we have only really used the sequential mode. Have used ARP, ICMP, IGMP, UDP, TCP using netconn and sockets API. Have also only been testing on devices with a single network interface. > > Also, have you been able to run the eCos tests for lwIP? We have had httpd_sequential and httpd_simple both working fine. We'll take a look at running more of the tests. > > Finally, can you confirm that all the eCos patches (changes relative to > upstream lwIP 1.3.2) have been applied to lwIP 1.4.1? I appreciate that the > PPP-related patches will have been dropped in favour of the new lwIP > implementation. Yes I believe so. Most of the eCos patches for lwip since the move to lwIP 1.3.2 have been in the eCos wrapper not the actual lwIP code. We have left the wrapper untouched except where needed. Patch 4 contains all the previous modifications to lwIP code and is just reapplying part of the commit "cdl/lwip_net.cdl: New CDL option CYGSEM_LWIP_MEM_SECTION." The two other commits to lwIP code were "Fix compiler warning about unused variables. [Bugzilla 1001521]" and "src/core/snmp/msg_out.c: Applied lwip bugfix #29256." both of which are dealt with now in the upstream lwIP 1.4.1 code > > Thanks > > John Dallaway -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-09-06 7:01 UTC|newest] Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-28 6:50 [Bug 1001873] New: " bugzilla-daemon 2013-06-28 6:50 ` [Bug 1001873] " bugzilla-daemon 2013-06-28 6:50 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:52 ` bugzilla-daemon 2013-06-28 6:52 ` bugzilla-daemon 2013-06-30 22:03 ` bugzilla-daemon 2013-07-01 11:54 ` bugzilla-daemon 2013-07-01 11:55 ` bugzilla-daemon 2013-07-01 11:56 ` bugzilla-daemon 2013-07-01 11:56 ` bugzilla-daemon 2013-07-01 11:56 ` bugzilla-daemon 2013-07-01 11:56 ` bugzilla-daemon 2013-07-01 11:57 ` bugzilla-daemon 2013-07-01 11:57 ` bugzilla-daemon 2013-07-01 11:57 ` bugzilla-daemon 2013-07-01 11:58 ` bugzilla-daemon 2013-07-01 13:34 ` bugzilla-daemon 2013-08-09 16:13 ` bugzilla-daemon 2013-08-10 15:51 ` bugzilla-daemon 2013-09-06 7:01 ` bugzilla-daemon [this message] 2013-09-06 7:01 ` bugzilla-daemon 2014-02-25 15:44 ` bugzilla-daemon 2014-02-25 15:46 ` bugzilla-daemon 2014-02-25 15:47 ` bugzilla-daemon 2014-02-25 15:48 ` bugzilla-daemon 2014-02-25 15:48 ` bugzilla-daemon 2014-02-25 15:48 ` bugzilla-daemon 2014-02-25 15:49 ` bugzilla-daemon 2014-02-25 15:49 ` bugzilla-daemon 2014-02-25 15:50 ` bugzilla-daemon 2014-02-25 16:09 ` bugzilla-daemon 2014-02-25 16:09 ` bugzilla-daemon 2014-03-12 9:17 ` bugzilla-daemon 2014-03-12 9:36 ` bugzilla-daemon 2014-05-05 23:08 ` bugzilla-daemon 2014-06-04 14:38 ` bugzilla-daemon 2014-06-05 10:06 ` bugzilla-daemon 2014-06-06 7:46 ` bugzilla-daemon 2014-06-10 8:27 ` bugzilla-daemon 2014-06-10 11:05 ` bugzilla-daemon 2013-06-28 6:50 [Bug 1001873] New: " bugzilla-daemon 2013-06-28 6:50 ` [Bug 1001873] " bugzilla-daemon 2013-06-28 6:50 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:51 ` bugzilla-daemon 2013-06-28 6:52 ` bugzilla-daemon 2013-06-28 6:52 ` bugzilla-daemon 2013-06-30 22:03 ` bugzilla-daemon 2013-07-01 11:54 ` bugzilla-daemon 2013-07-01 11:55 ` bugzilla-daemon 2013-07-01 11:55 ` bugzilla-daemon 2013-07-01 11:56 ` bugzilla-daemon 2013-07-01 11:56 ` bugzilla-daemon 2013-07-01 11:56 ` bugzilla-daemon 2013-07-01 11:57 ` bugzilla-daemon 2013-07-01 11:57 ` bugzilla-daemon 2013-07-01 11:57 ` bugzilla-daemon 2013-07-01 11:58 ` bugzilla-daemon 2013-07-01 13:34 ` bugzilla-daemon 2013-08-09 16:13 ` bugzilla-daemon 2013-08-10 15:51 ` bugzilla-daemon 2013-09-06 7:00 ` bugzilla-daemon 2013-09-06 7:01 ` bugzilla-daemon 2013-09-13 20:30 ` bugzilla-daemon 2014-02-15 2:58 ` bugzilla-daemon 2014-02-25 15:44 ` bugzilla-daemon 2014-02-25 15:46 ` bugzilla-daemon 2014-02-25 15:47 ` bugzilla-daemon 2014-02-25 15:48 ` bugzilla-daemon 2014-02-25 15:48 ` bugzilla-daemon 2014-02-25 15:48 ` bugzilla-daemon 2014-02-25 15:49 ` bugzilla-daemon 2014-02-25 15:49 ` bugzilla-daemon 2014-02-25 15:50 ` bugzilla-daemon 2014-02-25 16:09 ` bugzilla-daemon 2014-02-25 16:09 ` bugzilla-daemon 2014-03-11 22:25 ` bugzilla-daemon 2014-05-07 14:57 ` bugzilla-daemon 2014-06-04 14:38 ` bugzilla-daemon 2014-06-06 7:46 ` bugzilla-daemon 2014-06-10 8:27 ` bugzilla-daemon
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=bug-1001873-13-ipyJEoz9bX@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-bugs@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: linkBe 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).