From: Ilija Kocho <ilijak@siva.com.mk>
To: ecos-devel@ecos.sourceware.org
Subject: Re: Announcement of eCos porting to Freescale Kinetis - Cortex-M4
Date: Wed, 08 Dec 2010 20:43:00 -0000 [thread overview]
Message-ID: <4CFFEDFF.9010503@siva.com.mk> (raw)
In-Reply-To: <4CFFA78C.3010105@dallaway.org.uk>
Hi John
On 08.12.2010 16:43, John Dallaway wrote:
> Hi Ilija
>
> Ilija Kocho wrote:
>
>> We are announcing our work on eCos port to Fresscale's Kinetis Cortex-M4
>> controller family.
>> http://www.freescale.com/kinetis
>>
>> The initial port shall consist of:
>> - Kinetis Variant (with eventual Cortex-M architecture adjustments
>> if necessary);
>> - TWR-K60N512 Platform;
>> - Serial device driver (UART);
>> - Ethernet driver (may come little bit later);
> That is excellent news, thank you for the notification. It would be
> great if you could structure the variant package to accommodate future
> support for the K10/K20/K30/K40 parts if and where this might be
> appropriate.
Many thanks for words of encouragement and for hints.
I haven't browsed manuals of all Kinetis members, but I'll aim for
having all under a single variant (if possible without too much clutter
in sources).
I haven't looked at the details of all family members but from
Freescale's overviews it seems that with exception of Segment Display
Controller K60 is superset of other devices. I hope (but can't promise)
to get everything under a single platform CDL.
>> We shall contribute the port so I would ask for project registration.
> Now added to the table:
>
> http://ecos.sourceware.org/contrib.html#registered
Many thanks for registration.
Best regards
Ilija Kocho
prev parent reply other threads:[~2010-12-08 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 21:24 Ilija Kocho
2010-12-08 15:43 ` John Dallaway
2010-12-08 20:43 ` 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=4CFFEDFF.9010503@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=ecos-devel@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).