From: John Eigelaar <john@kses.net>
To: John Dallaway <john@dallaway.org.uk>
Cc: Frank Pagliughi <fpagliughi@mindspring.com>,
eCos Development List <ecos-devel@ecos.sourceware.org>
Subject: Re: eCos on AT91SAM9 - call to action
Date: Thu, 16 Jun 2011 14:16:00 -0000 [thread overview]
Message-ID: <1308233778.22353.4.camel@hp-study> (raw)
In-Reply-To: <4DFA0DAA.3000601@dallaway.org.uk>
> > Has anyone started work on the SAM3's?
> > How can I help?
>
> I am not aware of anyone working with eCos on AT91SAM3 hardware. There
> are existing Cortex-M variant ports for eCos on LM3S8xx, LPC17xx and
> STM32 processor families so I would expect variant support for AT91SAM3
> to be fairly straightforward. Hopefully some of the existing AT91
> drivers can be reused for AT91SAM3.
>
> I am sure that others within the eCos community will be interested in
> variant support for AT91SAM3. Be sure to let us all know if/when you
> start work on this.
We, Keystone Electronic Solutions, did a port for the AT91SAM3U. The
port was completed and was using most of the AT91 drivers from the SAM7
family. We have, however, decided to use an STM32 part instead of the
SAM3. The port is still available if anybody is interested
> John Dallaway
> eCos maintainer
> http://www.dallaway.org.uk/john
next prev parent reply other threads:[~2011-06-16 14:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 11:16 John Dallaway
2011-03-16 13:40 ` Grant Edwards
2011-03-16 14:31 ` AW: " Richard Rauch
2011-03-16 17:07 ` Martin Laabs
2011-03-16 18:18 ` John Dallaway
2011-03-16 18:35 ` Michael Bergandi
2011-03-17 10:14 ` Martin Laabs
2011-03-17 13:13 ` John Eigelaar
2011-06-16 13:38 ` Frank Pagliughi
2011-06-16 14:05 ` John Dallaway
2011-06-16 14:16 ` John Eigelaar [this message]
2011-06-16 14:27 ` eCos on AT91SAM3 [ was Re: eCos on AT91SAM9 - call to action ] John Dallaway
2011-06-16 14:29 ` eCos on AT91SAM9 - call to action Frank Pagliughi
2011-06-20 15:18 ` Eagle 100 (Stellaris LM3S6918) Frank Pagliughi
2011-06-20 16:17 ` Stanislav Meduna
2011-06-21 11:05 ` John Dallaway
2011-06-21 16:34 ` Christophe Coutand
2011-06-23 14:31 ` John Dallaway
2011-06-23 16:48 ` Frank Pagliughi
2011-06-23 17:57 ` Christophe Coutand
2011-07-10 20:38 ` Ilija Kocho
2011-07-12 8:57 ` Christophe Coutand
2011-07-13 14:52 ` Ilija Kocho
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=1308233778.22353.4.camel@hp-study \
--to=john@kses.net \
--cc=ecos-devel@ecos.sourceware.org \
--cc=fpagliughi@mindspring.com \
--cc=john@dallaway.org.uk \
/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).