From: Frank Pagliughi <fpagliughi@mindspring.com>
To: John Eigelaar <john@kses.net>
Cc: John Dallaway <john@dallaway.org.uk>,
eCos Development List <ecos-devel@ecos.sourceware.org>
Subject: Re: eCos on AT91SAM9 - call to action
Date: Thu, 16 Jun 2011 13:38:00 -0000 [thread overview]
Message-ID: <4DFA071F.4060504@mindspring.com> (raw)
In-Reply-To: <4D8208F0.5010500@kses.net>
On 03/17/2011 09:13 AM, John Eigelaar wrote:
> On 16/03/2011 13:16, John Dallaway wrote:
>> All
>>
>> There has been a lot of delay in getting AT91SAM9 support into the eCos
>> repository. Far too much delay. I think the best way forward now is to
>> focus on Evgeniy Dushitov's contribution (port for AT91SAM9263)
>> initially:
>>
>> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000819
>>
>> This seems sensible because:
>>
>> a) The patches themselves are well abstracted.
>> b) Some people are already using these patches as a baseline for
>> further AT91SAM9 ports.
>> c) There is support for running this port under QEMU, allowing
>> wider testing.
>>
>> I would like to invite everyone with an interest in AT91SAM9 support for
>> eCos to add themselves to the CC list for bug 1000819 and contribute to
>> the review process. Let's make this a community effort.
>>
>> John Dallaway
>> eCos maintainer
>> http://www.dallaway.org.uk/john
> John
> We, Keystone Electronic Solutions, have already done a Redboot port
> for the AT91SAM9X512 and AT91SAM9260 devices based on Evgeniy's
> patches if anybody is interested. I have no idea as to how up to date
> our patch is but I will be will to provide our source if anybody is
> interested.
>
> I have also used the port to build some test applications for these
> devices but nothing enterprise level yet. We use the Redboot port as
> boot loader for our Linux platforms.
>
> I have a personal copyright assignment for eCos, but will probably
> need a blanket company wide in order to contribute this work.
>
> Regards
> John Eigelaar
>
Hey All,
What's the latest news on the AT91 chip sets? From Bugzilla it appears
that there will be some reshuffling. I've been away from eCos for a few
years, but am looking to start a project with a legacy AT91 then
hopefully move it to a SAM3 in a few months.
Has anyone started work on the SAM3's?
How can I help?
Frank
next prev parent reply other threads:[~2011-06-16 13:38 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 [this message]
2011-06-16 14:05 ` John Dallaway
2011-06-16 14:16 ` John Eigelaar
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=4DFA071F.4060504@mindspring.com \
--to=fpagliughi@mindspring.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
--cc=john@kses.net \
/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).