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 1001186] Introduce Cortex-M4 to the Cortex-M architecture
Date: Wed, 06 Apr 2011 13:15:00 -0000	[thread overview]
Message-ID: <20110406131527.77EF22F78001@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001186-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=1001186

Nick Garnett <nickg@ecoscentric.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nickg@ecoscentric.com

--- Comment #3 from Nick Garnett <nickg@ecoscentric.com> 2011-04-06 14:15:25 BST ---
The M4 stuff looks OK to me.

However, I am not sure that we need the M0 option. The v6-M architecture is a
severely cut down version of the v7-M architecture. It lacks a lot of the
features we currently use in the Cortex-M HAL. Things like the dual stack
pointers, SVC, PendSVC and SysTick are only available if the OS option is
enabled. Other things like the programmable vector table base address and the
BASEPRI register are entirely absent.

Adding M0 to the list would raise entirely false expectations that this
processor type was supported. In fact, I would prefer to remove M1, since these
parts have the same problems.

We would have to do quite a lot of work to support M0/1. Given that these parts
are targeted at very low resource systems, I doubt that there will ever be much
demand for eCos on these.

-- 
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-04-06 13:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-03  8:44 [Bug 1001186] New: " bugzilla-daemon
2011-04-03  9:28 ` [Bug 1001186] " bugzilla-daemon
2011-04-05 18:33 ` bugzilla-daemon
2011-04-05 18:39 ` bugzilla-daemon
2011-04-06 13:15 ` bugzilla-daemon [this message]
2011-04-06 15:42 ` bugzilla-daemon
2011-04-06 15:55 ` bugzilla-daemon
2011-04-06 16:08 ` bugzilla-daemon
2011-04-06 16:15 ` bugzilla-daemon
2011-04-06 16:20 ` bugzilla-daemon
2011-04-06 16:31 ` bugzilla-daemon
2011-04-06 16:40 ` bugzilla-daemon
2011-04-06 16:58 ` bugzilla-daemon
2011-04-06 16:59 ` bugzilla-daemon
2011-04-06 17:09 ` 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=20110406131527.77EF22F78001@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).