public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Simon Kallweit <simon.kallweit@intefo.ch>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: lwip 1.3.1 testing
Date: Wed, 26 Aug 2009 20:46:00 -0000	[thread overview]
Message-ID: <20090826204512.GA2940@ubuntu.local> (raw)
In-Reply-To: <4A94D872.3000606@intefo.ch>

[-- Attachment #1: Type: text/plain, Size: 842 bytes --]

On Wed, Aug 26, 2009 at 08:38:42AM +0200, Simon Kallweit wrote:
> Sergei Gavrikov wrote:
>> On Tue, Aug 25, 2009 at 03:08:20PM +0300, Sergei Gavrikov wrote:
>>> On Tue, Aug 25, 2009 at 09:41:13AM +0200, Simon Kallweit wrote:
>>>> Hi
>>>>
>>>> I have done a new lwip test release with the following changes:
>>>>
>>>> * incorporated Sergei's patch (ctrl-c support)
>>>> * added an lwip_eth_simple and lwip_eth_sequential template
>>>>
>>>> The new test release can be downloaded from   
>>>> http://download.westlicht.ch/lwip-20090825.tar.gz

Hi

Simon, ya 2 cents. I found that the eth_tread's stack size is redefined
in sequential.c:101. First, that stack size is defined in the package's
header via CDL option. It seems the redefinition in sequetial.c can be
quite removed, otherwise the CDL value (eth stack size) wont be applied.

Sergei

[-- Attachment #2: sequential.c.patch --]
[-- Type: text/x-diff, Size: 481 bytes --]

diff -r bed5605f7e6d net/lwip_tcpip/current/src/ecos/sequential.c
--- a/net/lwip_tcpip/current/src/ecos/sequential.c	Tue Aug 25 18:32:48 2009 +0300
+++ b/net/lwip_tcpip/current/src/ecos/sequential.c	Wed Aug 26 23:28:54 2009 +0300
@@ -98,8 +98,6 @@
 CYG_HAL_TABLE_BEGIN(__NETDEVTAB__, netdev);
 CYG_HAL_TABLE_END(__NETDEVTAB_END__, netdev);
 
-#define ETH_THREAD_STACK_SIZE CYGNUM_HAL_STACK_SIZE_TYPICAL
-
 static sys_thread_t eth_thread_handle;
 static cyg_sem_t eth_thread_sem;
 

  parent reply	other threads:[~2009-08-26 20:46 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 [this message]
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
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=20090826204512.GA2940@ubuntu.local \
    --to=sergei.gavrikov@gmail.com \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=simon.kallweit@intefo.ch \
    /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).