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 16:08:00 -0000	[thread overview]
Message-ID: <20110406160747.3392E2F7800A@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

--- Comment #6 from Ilija Kocho <ilijak@siva.com.mk> 2011-04-06 17:07:45 BST ---
(In reply to comment #5)
> (In reply to comment #4)
> 
> > Nick, thank you for your expert look and explanation. So then, should I
> > reject the M0 (and M1?) mentions from the cortexm config file?
> 
> My opinion is that we should not add M0, and I think M1 should be removed until
> we have real support for that variant. I added M1 to the list early on in
> development, before I fully understood the actual differences between the v6-M
> and v7-M architectures.

Thank you for your review Nick. I had the same concerns regarding M0 and I
added it mainly because of presence of M1. I agree with you to omit M0 and M1.
Should anybody decide to port eCos to M0/M1 the easiest part of the job is to
put an entry in the legal values.

Note: Also we have to change the description. I propose to keep only offered
values (M3 M4) there too.

If you agree and this is all I could prepare a new patch for review.

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:[~2011-04-06 16:08 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
2011-04-06 15:42 ` bugzilla-daemon
2011-04-06 15:55 ` bugzilla-daemon
2011-04-06 16:08 ` bugzilla-daemon [this message]
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=20110406160747.3392E2F7800A@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).