From: Ilija Kocho <ilijak@siva.com.mk>
To: Bin Shi <powerman1st@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Question about support for modern arm architectures
Date: Thu, 15 Sep 2011 23:51:00 -0000 [thread overview]
Message-ID: <4E728F55.70905@siva.com.mk> (raw)
In-Reply-To: <CAHpUcor0OKpHBajDBY3xkB32hxgp-ukW76fesZeVPosYiHR02g@mail.gmail.com>
On 13.09.2011 09:24, Bin Shi wrote:
> Hi,
>
> I read the ecos official web site and found that the ARM board
> supported were all based arm9 which was old now.
>
> Is there any dev plan for modern arm architecture like cortex-a8, and arm11 ?
It seems that these Cortex-A application engineers are closer to general
purpose OSses like Linux and Android.
Regarding recent architectures, eCos has quite good support for Cortex-M.
Ilija
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2011-09-15 23:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 7:24 Bin Shi
2011-09-15 23:51 ` Ilija Kocho [this message]
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=4E728F55.70905@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=powerman1st@gmail.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).