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 1001125] New HAL for the Stellaris EK-LM3S811 board
Date: Mon, 31 Jan 2011 17:30:00 -0000	[thread overview]
Message-ID: <20110131173035.2B3E12F78003@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001125-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=1001125

--- Comment #17 from John Dallaway <john@dallaway.org.uk> 2011-01-31 17:30:33 GMT ---
(In reply to comment #10)

> > Nice thing Christophe, Small is beautiful.  This port may open door to
> > a big number of devices as nearly every manufacturer has Cortex-M
> > devices with 32KiB flash / 8KiB RAM (and below).
> > 
> > [ To decision makers ]
> > 
> > What about "lite" or "tiny" template?
> > "minimal" + kernel + some memory tuning, (like in default_ROM.ecm)
> 
> AFAIK, it cannot be managed only with a template. I agreed that if n00b
> cannot compile "hello, world!" via diag_printf() using minimal template,
> it is our pain (that is famous 32K stack size issue), also I have doubts
> about ~1/2 eCos kernel tests which use stacks like STACK_SIZE_TYPICAL x
> N. Ilija, it does not seem to me that all decision makers and experts on
> CC list of the Bug 1001125, so, I would raise the discussion on the same
> subject on ecos-devel list.

Appropriate stack sizes become critical on small memory targets and may become
highly dependent on the application. It would be wrong to _force_ the developer
into using certain stack sizes. Nevertheless, it would be helpful for new users
to be able to build some tests easily. One possibility is a "Constrain stack
sizes" CDL option in the platform HAL or variant HAL which 'requires' certain
stack sizes. It could be enabled by default to help new users and then disabled
when users gain more experience and can make decisions for themselves.

-- 
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:[~2011-01-31 17:30 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-1001125-104@http.bugs.ecos.sourceware.org/>
2011-01-23  9:06 ` bugzilla-daemon
2011-01-23  9:07 ` bugzilla-daemon
2011-01-23 18:46 ` bugzilla-daemon
2011-01-23 21:49 ` bugzilla-daemon
2011-01-27 18:23 ` bugzilla-daemon
2011-01-27 18:53 ` bugzilla-daemon
2011-01-31 10:48 ` bugzilla-daemon
2011-01-31 11:38 ` bugzilla-daemon
2011-01-31 12:32 ` bugzilla-daemon
2011-01-31 12:37 ` bugzilla-daemon
2011-01-31 12:48 ` bugzilla-daemon
2011-01-31 13:09 ` bugzilla-daemon
2011-01-31 13:16 ` bugzilla-daemon
2011-01-31 13:18 ` bugzilla-daemon
2011-01-31 13:41 ` bugzilla-daemon
2011-01-31 17:30 ` bugzilla-daemon [this message]
2011-01-31 19:43 ` bugzilla-daemon
2011-01-31 19:45 ` bugzilla-daemon
2011-01-31 20:01 ` bugzilla-daemon
2011-01-31 20:17 ` bugzilla-daemon
2011-02-04 13:37 ` bugzilla-daemon
2011-02-06 12:14 ` bugzilla-daemon
2011-02-06 12:23 ` bugzilla-daemon
2011-02-06 13:28 ` bugzilla-daemon
2011-02-06 14:45 ` bugzilla-daemon
2011-02-06 14:53 ` bugzilla-daemon
2011-02-06 15:35 ` bugzilla-daemon
2011-02-08 18:26 ` bugzilla-daemon
2011-02-08 22:02 ` bugzilla-daemon
2011-02-08 22:26 ` bugzilla-daemon
2011-02-09  1:25 ` bugzilla-daemon
2011-02-09  1:26 ` bugzilla-daemon
2011-02-09  8:24 ` bugzilla-daemon
2011-02-09  8:39 ` bugzilla-daemon
2011-02-09 18:30 ` bugzilla-daemon
2011-02-09 18:36 ` bugzilla-daemon
2011-02-09 20:58 ` bugzilla-daemon
2011-02-09 21:28 ` bugzilla-daemon
2011-02-09 22:21 ` bugzilla-daemon
2011-02-11 16:38 ` bugzilla-daemon
2011-02-18 15: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=20110131173035.2B3E12F78003@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).