public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Simon Kallweit <simon.kallweit@intefo.ch>
To: Grant Edwards <grante@visi.com>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS]  Re: Cortex M3 architecture
Date: Tue, 02 Sep 2008 11:34:00 -0000	[thread overview]
Message-ID: <48BD247D.20106@intefo.ch> (raw)
In-Reply-To: <48BC005E.3030807@intefo.ch>

Simon Kallweit schrieb:
> Andrew Lunn schrieb:
>>> I would think that Thumb2 processors like the M3 would need to
>>> be a different architecture than ARM.  It's a different
>>> instruction set -- isn't that what defines an architecture?
>>>     
>>
>> With ARM it is all a bit messy. eg some of the processors support
>> thumb2 as an add on, just like the support thumb. For such processors,
>> you could add thumb2 support to the existing ARM architecture, with
>> the understanding that all interrupt handling is done in the good old
>> ARM instruction set. However user code could be in thumb/thumb2.
>>
>> For the Cortex M processors you cannot do this, so a new architecture
>> is needed when you _only_ have thumb/thumb2.
>>   
> So, I guess we should introduce a new architecture named "armv7m". I 
> think this makes sense as we can then support both M3 and M1 as 
> variants. What do you think?
>

I still wonder what we should use as the architecture name. "armv7m" is 
obviously wrong, as the M1 is actually an armv6m. So, should the new 
architecture be named "cortex", or maybe "cortexm"? Any ideas are very 
welcome.

Simon

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2008-09-02 11:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01 13:19 [ECOS] " simon.kallweit
2008-09-01 13:38 ` Andrew Lunn
2008-09-01 13:48   ` simon.kallweit
2008-09-01 14:20     ` Andrew Lunn
2008-09-01 14:32     ` [ECOS] " Grant Edwards
2008-09-01 14:41       ` Andrew Lunn
2008-09-01 14:47         ` Simon Kallweit
2008-09-02 11:34           ` Simon Kallweit [this message]
2008-09-03  7:15             ` Robin Randhawa
2008-09-03  7:27               ` simon.kallweit
2008-09-03  7:42                 ` Robin Randhawa
2008-09-03  8:07                   ` simon.kallweit
2008-09-05  6:19                     ` Robin Randhawa
2008-09-03  7:50             ` Andrew Lunn
2008-09-03  8:17               ` simon.kallweit
2008-09-03  8:29                 ` Andrew Lunn

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=48BD247D.20106@intefo.ch \
    --to=simon.kallweit@intefo.ch \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=grante@visi.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).