From: Andrew Lunn <andrew@lunn.ch>
To: Moussa Ba <mba@embedded-zone.com>
Cc: Andrew Lunn <andrew@lunn.ch>, ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Build Error when Compiling redboot
Date: Tue, 06 Jun 2006 07:18:00 -0000 [thread overview]
Message-ID: <20060606071751.GQ2478@lunn.ch> (raw)
In-Reply-To: <4481A6C1.3010807@embedded-zone.com>
On Sat, Jun 03, 2006 at 11:12:01AM -0400, Moussa Ba wrote:
> Thank you I had went back and figured it out from the RedBoot manual.
> Thank you for the help. I have recompiled the mcb2100 version of ecos,
> and to save RAM I decreased the stack size allocated to the main from
> 8192 to 2048 is this reasonable, I don't expect to be going too deep in
> the stack but I am not sure if ecos related functions needed this much.
You need to watch out for diag_printf(). It can use a lot of stack.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2006-06-06 7:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 21:56 Moussa A. Ba
2006-06-01 22:52 ` Gary Thomas
2006-06-02 20:11 ` Moussa Ba
2006-06-03 8:09 ` Andrew Lunn
2006-06-03 15:12 ` Moussa Ba
2006-06-06 7:18 ` Andrew Lunn [this message]
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=20060606071751.GQ2478@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=mba@embedded-zone.com \
/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).