This is the mail archive of the
mailing list for the eCos project.
[Bug 1001186] Introduce Cortex-M4 to the Cortex-M architecture
- From: bugzilla-daemon at bugs dot ecos dot sourceware dot org
- To: ecos-patches at ecos dot sourceware dot org
- Date: Wed, 6 Apr 2011 17:07:47 +0100
- Subject: [Bug 1001186] Introduce Cortex-M4 to the Cortex-M architecture
- Auto-submitted: auto-generated
- References: <email@example.com/>
Please do not reply to this email. Use the web interface provided at:
--- Comment #6 from Ilija Kocho <firstname.lastname@example.org> 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.
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.