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: Thu, 05 Jun 2014 10:06:00 -0000	[thread overview]
Message-ID: <bug-1001873-13-gjNAqE6fD1@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1001873-13@http.bugs.ecos.sourceware.org/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 5676 bytes --]

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001873

--- Comment #45 from Ilija Kocho [Илија Кочо] <ilijak@siva.com.mk> ---
(In reply to comment #44)

Hi Oleg

Thank you for your feedback.

> Hi Guys,
> 
> First and foremost thank you very much for the patches provided here.
> 
> I have successfully upgraded lwip 1.3.2 to vanilla lwip 1.4.1 in ecos using
> consolidated patch 1-13 kindly provided by Illija. BTW, I tested PPP on
> stm32f4-discovery and it works (but for some reason less stable than ppp in
> lwip 1.3.2, I can provide more info if requested).

I would appreciate if you do so.

> 
> There have been some major changes since vanilla lwip 1.4.1 commit in
> particular ppp-new has been merged into master branch. Since the nature of
> my project depends on lwip ppp implementation, I would like to use its most
> recent version.
> 

I assume it that by vanilla "lwip 1.4.1" you mean the lwIP 1.4.1 release, and
the other is current lwIP source (from GIT). Am I right?


> Please, suggest how to go about upgrading vanilla lwip 1.4.1 in ecos to the
> most new version of lwip 1.4.1.
> 

Assuming that my assumption above is right...

I would:

  1. download vanilla lwIP 1.4.1 master. (i.e. without eCos). ->
lwip-1.4.1-master
  2. download or check out current lwIP source (i.e. the source that I want to
upgrade to. -> lwip-current
  3. Diff 2. vs 1. Something like: diff -ruN lwip-1.4.1-master lwip-current
>lwip_upgrqade.diff

  4. Study lwip_upgrade.diff and try to apply changes to eCos' lwIP 1.4.1. With
little luck it may be possible to just patch it over eCos lwIP.

I hope this helps and I'd appreciate some feedback.

Ilija

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From ecos-bugs-return-10827-listarch-ecos-bugs=sources.redhat.com@sourceware.org Thu Jun 05 22:36:56 2014
Return-Path: <ecos-bugs-return-10827-listarch-ecos-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-ecos-bugs@sources.redhat.com
Received: (qmail 21137 invoked by alias); 5 Jun 2014 22:36:56 -0000
Mailing-List: contact ecos-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <ecos-bugs.sourceware.org>
List-Subscribe: <mailto:ecos-bugs-subscribe@sourceware.org>
List-Post: <mailto:ecos-bugs@sourceware.org>
List-Help: <mailto:ecos-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: ecos-bugs-owner@sourceware.org
Delivered-To: mailing list ecos-bugs@sourceware.org
Received: (qmail 21122 invoked by uid 89); 5 Jun 2014 22:36:54 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO: mail.ecoscentric.com
Received: from Unknown (HELO mail.ecoscentric.com) (212.13.207.200)
 by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 05 Jun 2014 22:36:52 +0000
Received: from localhost (localhost [127.0.0.1])
	by mail.ecoscentric.com (Postfix) with ESMTP id 4B102A83D4A
	for <ecos-bugs@ecos.sourceware.org>; Thu,  5 Jun 2014 23:36:50 +0100 (BST)
Received: from mail.ecoscentric.com ([127.0.0.1])
	by localhost (albus.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xTLl1YGESjpS for <ecos-bugs@ecos.sourceware.org>;
	Thu,  5 Jun 2014 23:36:45 +0100 (BST)
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001989] New: Cortex-M linker script template does not accept
 user selectable grouped libraries.
Date: Thu, 05 Jun 2014 22:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: eCos
X-Bugzilla-Component: HAL
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: ilijak@siva.com.mk
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: low
X-Bugzilla-Assigned-To: unassigned@bugs.ecos.sourceware.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter cc
Message-ID: <bug-1001989-13@http.bugs.ecos.sourceware.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://bugs.ecos.sourceware.org/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014/txt/msg00194.txt.bz2
Content-length: 1116

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id\x1001989

            Bug ID: 1001989
           Summary: Cortex-M linker script template does not accept user
                    selectable grouped libraries.
           Product: eCos
           Version: CVS
            Target: All
  Architecture/Host Cortex-M
                OS:
            Status: NEW
          Severity: enhancement
          Priority: low
         Component: HAL
          Assignee: unassigned@bugs.ecos.sourceware.org
          Reporter: ilijak@siva.com.mk
                CC: ecos-bugs@ecos.sourceware.org

Created attachment 2514
  --> http://bugs.ecos.sourceware.org/attachment.cgi?id%14&actioníit
Fix Cortex-M linker script to accept user selectable grouped libraries.

eCos HAL macro CYGBLD_HAL_LINKER_GROUPED_LIBS provides for user selectable
grouped libraries.
In Cortex-M linker template cortexm.ld grouped libraries are hard coded. The
submitted attachment introduces the macro to linker script.

--
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-06-05 10:06 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
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 [this message]
2014-06-06  7:46 ` bugzilla-daemon
2014-06-10  8:27 ` bugzilla-daemon
2014-06-10 11:05 ` bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
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-gjNAqE6fD1@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: 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).