public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001344] Allow nc_test_slave for lwIP to compile for targets with 128KiB RAM.
Date: Sun, 13 May 2012 10:50:00 -0000	[thread overview]
Message-ID: <20120513104943.DEBCE2F78001@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001344-104@http.bugs.ecos.sourceware.org/>

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001344

Ilija Kocho <ilijak@siva.com.mk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #1384|0                           |1
        is obsolete|                            |

--- Comment #14 from Ilija Kocho <ilijak@siva.com.mk> 2012-05-13 11:49:36 BST ---
Created an attachment (id=1754)
 --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1754)
Reduce stack usage of nc_test_slave (MAX_BUF set to 12KiB)

(In reply to comment #13)
> (In reply to comment #12)
> > (In reply to comment #11)
> > > (In reply to comment #8)
> > > > (In reply to comment #6)
> > > > > Thus, no comments were here anymore. I would like commit the
> > > > > patch.  Jlija, can you provide the ChangeLog's record, please.
> > > > 
> > > > Here it is Sergei, thank you. I was waiting if somebody tries on
> > > > other architecture. In meantime we tested on X86 architecture -
> > > > works.
> > > 
> > > Ilija, thank you (I've got the latest).
> > > 
> > > I would try to test the modified test on some ARM7TDMI target (if you
> > > did not try the same) and may be on Linux synthetic.
> > 
> > Bad news. The stacks are too small to run the test on Linux synthetic
> > target (I've got 'Segmentation fault' with the patched version). It
> > seems we need investigate more time to get proper values for 'synth'
> > target and use another set of the values for CYGPKG_HAL_SYNTH.
> > 
> > Sergei

Here I am again after long time. It seem that buffers were too short 8KiB and
messages can be up to 10KiB. Now I fixed this and it is stable. Unfortunately I
can't test on synthetic target since newer Linux kernel (3) doesn't seem to
support ethertap (any suggestion?).
Sergei do u have some time to test on synthetic target pse?

Note: The same bug with MAX_BUF seem to be present in BSD test too. I'm going
to open a bug for that.

Ilija

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2012-05-13 10:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-26  7:28 [Bug 1001344] New: " bugzilla-daemon
2011-09-26 20:11 ` [Bug 1001344] " bugzilla-daemon
2011-09-26 21:30 ` bugzilla-daemon
2011-09-27  5:45 ` bugzilla-daemon
2011-09-27  7:35 ` bugzilla-daemon
2011-09-27  9:06 ` bugzilla-daemon
2011-10-02 14:36 ` bugzilla-daemon
2011-10-02 17:23 ` bugzilla-daemon
2011-10-02 17:29 ` bugzilla-daemon
2011-10-02 17:32 ` bugzilla-daemon
2011-10-02 17:36 ` bugzilla-daemon
2011-10-02 17:50 ` bugzilla-daemon
2011-10-02 19:06 ` bugzilla-daemon
2011-10-02 19:24 ` bugzilla-daemon
2012-05-13 10:50 ` bugzilla-daemon [this message]
2012-05-13 11:22 ` bugzilla-daemon
2012-05-14 20:36 ` bugzilla-daemon
2012-05-15  9:26 ` bugzilla-daemon
2012-05-15  9:55 ` bugzilla-daemon
2012-05-15 11:04 ` bugzilla-daemon
2012-05-16  0:28 ` bugzilla-daemon
2012-05-16 16:04 ` bugzilla-daemon
2012-05-16 16:20 ` bugzilla-daemon
2012-05-17 15:54 ` bugzilla-daemon
2012-05-17 16:12 ` bugzilla-daemon
2012-05-17 16:12 ` bugzilla-daemon
2012-05-17 17:04 ` bugzilla-daemon
2012-05-17 17:45 ` bugzilla-daemon
2012-05-18  7:25 ` bugzilla-daemon
2012-05-18 15:28 ` bugzilla-daemon
2012-05-26 19:19 ` bugzilla-daemon
2012-05-27  0:09 ` bugzilla-daemon
2012-05-27  8:32 ` 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=20120513104943.DEBCE2F78001@mail.ecoscentric.com \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-patches@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).